Techniques to facilitate a cloud-based vehicle xr experience

ABSTRACT

Apparatus, methods, and computer-readable media for facilitating a cloud-based vehicle XR user experience are disclosed herein. An example method for wireless communication at a user equipment (UE) includes transmitting a request for a vehicle extended reality (XR) session. The vehicle XR session may be based on a first user XR stream including a vehicle XR component associated with a vehicle and a first user XR component associated with a first user. The first user may have an association with the vehicle. The example method also includes transmitting uplink information associated with the first user XR stream. The example method also includes receiving rendering information associated with the first user XR stream. The rendering information may be based on the uplink information.

INTRODUCTION

The present disclosure relates generally to communication systems, andmore particularly, to wireless communications associated with extendedreality (XR) services.

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources. Examples of suchmultiple-access technologies include code division multiple access(CDMA) systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example telecommunication standardis 5G New Radio (NR). 5G NR is part of a continuous mobile broadbandevolution promulgated by Third Generation Partnership Project (3GPP) tomeet new requirements associated with latency, reliability, security,scalability (e.g., with Internet of Things (IoT)), and otherrequirements. 5G NR includes services associated with enhanced mobilebroadband (eMBB), massive machine type communications (mMTC), andultra-reliable low latency communications (URLLC). Some aspects of 5G NRmay be based on the 4G Long Term Evolution (LTE) standard. There existsa need for further improvements in 5G NR technology. These improvementsmay also be applicable to other multi-access technologies and thetelecommunication standards that employ these technologies.

BRIEF SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects. This summaryneither identifies key or critical elements of all aspects nordelineates the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method of wireless communication at auser equipment (UE) is provided. The method may include transmitting arequest for a vehicle extended reality (XR) session, the vehicle XRsession being based on a first user XR stream including a vehicle XRcomponent associated with a vehicle and a first user XR componentassociated with a first user, the first user having an association withthe vehicle. The example method may also include transmitting uplinkinformation associated with the first user XR stream. The example methodmay also include receiving rendering information associated with thefirst user XR stream, the rendering information being based on theuplink information.

In another aspect of the disclosure, an apparatus for wirelesscommunication is provided. The apparatus may be a UE that includes amemory and at least one processor coupled to the memory, the at leastone processor configured to transmit a request for a vehicle XR session,the vehicle XR session being based on a first user XR stream including avehicle XR component associated with a vehicle and a first user XRcomponent associated with a first user, the first user having anassociation with the vehicle. The at least one processor may also beconfigured to transmit uplink information associated with the first userXR stream. The at least one processor may also be configured to receiverendering information associated with the first user XR stream, therendering information being based on the uplink information.

In another aspect of the disclosure, an apparatus for wirelesscommunication at a UE is provided. The apparatus may include means fortransmitting a request for a vehicle XR session, the vehicle XR sessionbeing based on a first user XR stream including a vehicle XR componentassociated with a vehicle and a first user XR component associated witha first user, the first user having an association with the vehicle. Theexample apparatus may also include means for transmitting uplinkinformation associated with the first user XR stream. The exampleapparatus may also include means for receiving rendering informationassociated with the first user XR stream, the rendering informationbeing based on the uplink information.

In another aspect of the disclosure, a non-transitory computer-readablestorage medium storing computer executable code for wirelesscommunication at a UE is provided. The code, when executed, may cause aprocessor to transmit a request for a vehicle XR session, the vehicle XRsession being based on a first user XR stream including a vehicle XRcomponent associated with a vehicle and a first user XR componentassociated with a first user, the first user having an association withthe vehicle. The example code, when executed, may also cause theprocessor to transmit uplink information associated with the first userXR stream. The example code, when executed, may also cause the processorto receive rendering information associated with the first user XRstream, the rendering information being based on the uplink information.

In an aspect of the disclosure, a method of wireless communication at anetwork entity is provided. The method may include obtaining a requestfor a vehicle XR session. The method may also include authorizing thevehicle XR session, the vehicle XR session being based on a first userXR stream including a vehicle XR component associated with a vehicle anda first user XR component associated with a first user, the first userhaving an association with the vehicle. The example method may alsoinclude obtaining uplink information associated with the first user XRstream. Additionally, the example method may include outputtingrendering information associated with the first user XR stream, therendering information being based on the uplink information.

In another aspect of the disclosure, an apparatus for wirelesscommunication is provided. The apparatus may be a base station thatincludes a memory and at least one processor coupled to the memory, theat least one processor configured to obtain a request for a vehicle XRsession. The at least one processor may also be configured to authorizethe vehicle XR session, the vehicle XR session being based on a firstuser XR stream including a vehicle XR component associated with avehicle and a first user XR component associated with a first user, thefirst user having an association with the vehicle. The at least oneprocessor may also be configured to obtain uplink information associatedwith the first user XR stream. Additionally, the at least one processormay be configured to output rendering information associated with thefirst user XR stream, the rendering information being based on theuplink information.

In another aspect of the disclosure, an apparatus for wirelesscommunication at a base station is provided. The apparatus may includemeans for obtaining a request for a vehicle XR session associated. Theapparatus may also include means for authorizing the vehicle XR session,the vehicle XR session being based on a first user XR stream including avehicle XR component associated with a vehicle and a first user XRcomponent associated with a first user, the first user having anassociation with the vehicle. The example apparatus may also includemeans for obtaining uplink information associated with the first user XRstream. Additionally, the example apparatus may include means foroutputting rendering information associated with the first user XRstream, the rendering information being based on the uplink information.

In another aspect of the disclosure, a non-transitory computer-readablestorage medium storing computer executable code for wirelesscommunication at a base station is provided. The code, when executed,may cause a processor to obtain a request for a vehicle XR session. Theexample code, when executed, may also cause the processor to authorizethe vehicle XR session, the vehicle XR session being based on a firstuser XR stream including a vehicle XR component associated with avehicle and a first user XR component associated with a first user, thefirst user having an association with the vehicle. The example code,when executed, may also cause the processor to obtain uplink informationassociated with the first user XR stream. Additionally, the examplecode, when executed, may cause the processor to output renderinginformation associated with the first user XR stream, the renderinginformation being based on the uplink information.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe drawings set forth in detail certain illustrative features of theone or more aspects. These features are indicative, however, of but afew of the various ways in which the principles of various aspects maybe employed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network.

FIG. 2A is a diagram illustrating an example of a first frame, inaccordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of DL channels within asubframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, inaccordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of UL channels within asubframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and userequipment (UE) in an access network.

FIG. 4 is a diagram illustrating an example disaggregated base stationarchitecture, in accordance with the teachings disclosed herein

FIG. 5 is a diagram illustrating an example vehicle configured with avehicle XR system, in accordance with the teachings disclosed herein.

FIG. 6A is a diagram illustrating an example XR scene, in accordancewith the teachings disclosed herein.

FIG. 6B is a diagram illustrating an example scene including real worldobjects, in accordance with the teachings disclosed herein.

FIG. 6C is a diagram illustrating an example XR scene including virtualobjects superimposed on real world objects, in accordance with theteachings disclosed herein.

FIG. 7 is an example communication flow between a network entity, a UE,and a cloud XR entity, in accordance with the teachings disclosedherein.

FIG. 8 is an example communication flow between a network entity and aUE, in accordance with the teachings disclosed herein.

FIG. 9 is an example communication flow between a network entity and aUE, in accordance with the teachings disclosed herein.

FIG. 10 is a diagram illustrating example collected informationexchanged with a network entity, in accordance with the teachingsdisclosed herein.

FIG. 11 is an example communication flow between a network entity and aUE, in accordance with the teachings disclosed herein.

FIG. 12 is an example communication flow between a network entity and aUE, in accordance with the teachings disclosed herein.

FIG. 13 is an example communication flow between a network entity and aUE, in accordance with the teachings disclosed herein.

FIG. 14 is an example communication flow between a network entity and aUE, in accordance with the teachings disclosed herein.

FIG. 15 is an example communication flow between a network entity, a UE,and a service entity, in accordance with the teachings disclosed herein.

FIG. 16 is a flowchart of a method of wireless communication at a UE, inaccordance with the teachings disclosed herein.

FIG. 17 is a flowchart of a method of wireless communication at a UE, inaccordance with the teachings disclosed herein.

FIG. 18 is a diagram illustrating an example of a hardwareimplementation for an example apparatus and/or network entity.

FIG. 19 is a flowchart of a method of wireless communication at anetwork entity, in accordance with the teachings disclosed herein.

FIG. 20 is a flowchart of a method of wireless communication at anetwork entity, in accordance with the teachings disclosed herein.

FIG. 21 is a diagram illustrating an example of a hardwareimplementation for an example network entity.

FIG. 22 is a diagram illustrating an example of a hardwareimplementation for an example network entity.

DETAILED DESCRIPTION

Extended reality (XR) refers to the reality-virtuality continuum betweenreal environments and virtual environments. Extended realitytechnologies can provide virtual content to a user, and/or combine realor physical environments and virtual environments, which may be made upof virtual content or virtual objects, to provide users with XRexperiences. An XR experience may include virtual reality (VR),augmented reality (AR), mixed reality (MR), and/or other immersivecontent.

A user may experience XR (e.g., may be provided with an XR experience)via an XR device. Extended reality devices may be of different formfactors and may differ in processing capabilities, power consumption,and/or communication types. One example of an XR device is ahead-mounted display (HMD). The HMD may include a display positioned infront of one or both eyes. The display may stream data, images, and/orother information in front of the user's eye(s).

An HMD may include an optical system, such as a display and/or lenses,one or more tracking sensors, one or more cameras, communicationfunctionalities, and an XR engine. The XR engine may perform XR-relatedprocessing and may include one or more graphical processing units(GPUs), central processing units (CPUs), etc. The display of an HMD maybe transparent or not transparent. For example, for an AR application,the display may be transparent (or mostly transparent) and ARinformation may be superimposed onto real life objects. In anotherexample, for a VR application, the display may not be transparent andvirtual information and images may be displayed in front of the user'seyes.

One example application of XR is associated with vehicles. For example,a vehicle may be configured with an XR system that provides avehicle-based XR experience to users of the vehicle. The vehicle mayinclude a terrestrial vehicle, such as a car, a bus, a train, etc., oran airborne/non-terrestrial vehicle, such as a drone, a balloon, aplane, a helicopter, etc. The user of the vehicle may be a human, adevice with artificial intelligence, a communication equipmentsupporting remote access, or a connected controller. The XR system ofthe vehicle may have a different form factor than an HMD, but mayinclude one or more similar components. For example, a vehicle XR systemmay include one or more displays for presentment of renderinginformation, one or more sensors for collecting information at thevehicle, and a UE to facilitate communication functions and XR-basedprocessing. As used herein, a UE associated with a vehicle andconfigured to provide a vehicle-based XR experience may be referred toas a “vehicle UE,” a “vehicle XR system UE,” or, may be generallyreferred to as a “UE” herein.

As an example of a vehicle XR application, a navigation system of thevehicle may enable a user (e.g., a driver, a first passenger, etc.) toinput a desired destination and generate a path plan (e.g., a route) toarrive at the desired destination. The one or more sensors may capturevehicle-surrounding information of the area around the vehicle. Thevehicle UE may then process the vehicle-surrounding information andgenerate rendering information accordingly. One or more displays of thevehicle XR system may then display the rendering information. Forexample, the rendering information may include augmentation informationthat is superimposed on real world objects surrounding the vehicle.Non-limiting examples of real world objects surrounding the vehicle mayinclude traffic lights, hazard signs, road signs, barricades, landmarks,buildings, billboards, etc. The augmentation information may includedriver assistance information, such as a current speed of the vehicle, aspeed limit, gas-related or battery-related information, upcomingdirections, traffic light phasing information, information of potentialmaneuver of the surrounding vehicles and vulnerable road users (VRUs),road conditions, etc.

In some examples, the augmentation information presented to the user maybe based on what the vehicle UE is able to identify and then present viathe one or more displays. That is, the augmentation information may bebased on a static or local-processing-based mechanism. Examples ofstatic or local-processing-based mechanisms may be based onpre-configured information stored at the vehicle UE. For example, thevehicle UE may be configured with augmentation information correspondingto navigation, such as indicators of speed limits associated withstreets or highways. In some such examples, the vehicle UE may identify,based on information provided by the one or more sensors of the vehicleXR system, a real world object, such as a street sign. According to oneor more examples, the vehicle UE may then display augmentationinformation indicating the speed limit associated with the street basedon the identified street sign.

In some examples, the augmentation information may be generated anddisplayed via the one or more displays of the vehicle XR systemregardless of where the driver or the user is looking. For example, adisplay associated with the front windshield of the vehicle may displaythe augmentation information indicating the speed limit while the driveris looking out a side window of the vehicle. In such examples, the UEmay be using resources (e.g., processing resources, memory, etc.) togenerate and present the augmentation information with certain defaultconfigurations. Additionally, in some examples, the augmentationinformation presented in an XR scene may be limited to what objects theUE is able to identify and/or may be limited to the information providedby another system of the vehicle, such as the navigation system.

However, it may be appreciated that as more complicated vehicle XRoperation scenarios emerge, the static or local-processing-basedmechanism (or systems) may be less suitable and/or less efficient toprovide a satisfactory user experience. For example, the static orlocal-processing-based mechanism of the vehicle XR system may not havethe ability to identify landmarks in real-time (or near real-time). Insome examples, the static or local-processing-based mechanism mayprovide inaccurate augmentation information. For example, the vehicle UEmay be configured with augmentation information associated with a firstlandmark that has been replaced with a second landmark since the vehicleUE was configured. For example, when the vehicle UE is configured withaugmentation information associated with an intersection, theaugmentation information may include additional information about aclothing store. However, after the vehicle UE was configured with theaugmentation information, the clothing store may have been replaced witha coffee shop.

Aspects disclosed herein facilitate a vehicle XR application thatincludes cloud-based processing. For example, aspects disclosed hereinenable offloading some processing associated with presentingaugmentation information to a cloud XR entity. The cloud XR entity maybe in communication with a vehicle UE of a vehicle XR system. The cloudXR entity may receive information collected from a vehicle UE via one ormore sensors of the vehicle XR system. The cloud XR entity may then helpdetermine what rendering information is needed to support the vehicle XRapplication at the vehicle and to provide a satisfactory user experience(e.g., an XR experience that may be appreciated by the user). Therendering information may include associated with XR information and mayfacilitate presentment of the XR information via the one or moredisplays of the vehicle XR system. Non-limiting examples of renderinginformation may include augmentation information, identifiers oflandmarks, interactive objects, additional information associated with areal world object, etc., that may be superimposed over real worldobjects and/or representations of real world objects. For example, thecloud XR entity may have the ability to identify real world objects inreal-time (or near real-time) based on the information received from thevehicle UE. For example, based on the information received from thevehicle UE, the cloud XR entity may have the ability to identify that anintersection has a clothing store and provide augmentation informationassociated with the clothing store.

In some aspects, the vehicle UE and the cloud XR entity may establish avehicle XR session. The vehicle XR session may enable communicationassociated with a user stream between the vehicle UE and the cloud XRentity. For example, the user stream may include uplink information thatis provided by the vehicle UE to the cloud XR entity. The user streammay also include downlink information that is provided by the cloud XRentity to the vehicle UE.

The uplink information may include information that is collected by theone or more sensors of the vehicle XR system. The uplink information mayinclude information about the vehicle and information about a user. Forexample, the collected information may include a vehicle XR componentthat includes one or more of vehicle pose information, vehicleinformation, and vehicle-surrounding information. The uplink informationmay also include a user XR component that includes one or more of userpose information and input information. The user pose information mayinclude information relating to a position and/or orientation of theuser in space relative to an XR space. An XR space may represent avirtual coordinate system with an origin that corresponds to a physicallocation. The user pose information may be with respect to the ground(e.g., absolute pose information) and/or with respect to the vehicle(e.g., relative pose information). The input information may includeinformation related to user eye tracking and/or user gestures.

The downlink information from the cloud XR entity to the vehicle UE mayinclude rendering information for presentment at the vehicle. Forexample, the rendering information may include XR information, such asaugmentation information, that the vehicle UE is configured tosuperimpose over real world objects. The vehicle UE may also display theXR information via the one or more displays of the vehicle XR system. Asused herein, the term “XR information” refers to information that isrendered in association with a vehicle XR session. For example, XRinformation may include augmentation information that the cloud XRentity generates for superimposing over real world objects.

The cloud XR entity may obtain the uplink information and performvirtual-physical fusion of the information to generate the renderinginformation. In one or more aspects, the virtual-physical fusion of theinformation may include identifying real world objects and XRinformation. For example, the cloud XR entity may identify the realworld objects based on the vehicle-surrounding information of thevehicle XR component of the uplink information. The cloud XR entity mayalso generate XR information based on the identified real world objects.In some examples, the cloud XR entity may generate the XR informationbased on information received from additional network entities. Forexample, the cloud XR entity may identify a sports stadium and obtain XRinformation associated with the sports stadium from a network entitythat provides sports-based information. The cloud XR entity may thenprovide the rendering information to the vehicle UE for presentment. Forexample, the vehicle UE may facilitate displaying the renderinginformation via the one or more displays of the vehicle.

Additionally, as XR systems and communication systems evolve and mature,more XR experiences may emerge. For example, rather than a vehicle XRapplication that displays information without taking driver informationinto account, the cloud XR entity could adapt the rendering informationprovided to the vehicle UE based on user pose. In such examples, the XRapplication may present information relevant to a user (e.g., thedriver) as the user moves their head and what the user is seeingchanges. The rendering information provided to the vehicle UE may beadjusted according to the status of the user, or the situation of thevehicle. For example, certain traffic related information may not bepresented to the user when the vehicle is parked. In another example,only driving related XR information may be presented to the driver whenthe vehicle is moving at higher speed.

Additionally, the cloud XR entity may allow passengers to be providedwith an XR experience. For example, the one or more sensors of thevehicle XR system may collect information associated with differentusers (e.g., a driver and one or more passengers). In some suchexamples, the cloud XR entity may have the ability to generate XRinformation for the different users. For example, passengers may bepresented with XR information that is the same or different than thedriver. For example, a driver may be presented with first XR informationthat is related to navigation (e.g., direction, speed, etc.) whilepassengers may be presented with second XR information related tolandmarks. According to one or more examples, the XR informationpresented to the passengers may be shielded from the view of the driver,for example, to avoid distracting the driver.

In some examples, the rendering information provided to the vehicle UEmay include interactive objects with which the user may engage. In someexamples, engaging with the interactive object may provide additionalinformation about real world objects. For example, an interactive objectmay be superimposed above a landmark. In some examples, a user mayengage with (e.g., select) the interactive object to receive informationabout the landmark. In some examples, a user may engage with theinteractive object to perform a transaction. For example, the renderinginformation may include an interactive object that is superimposed abovea coffee shop. In some examples, the user may select the interactiveobject to initiate a coffee purchase at the coffee shop. In someexamples, the input information of the user XR component may includeinformation indicating engagement with the interactive object.

In some examples, the vehicle UE may provide relatively frequentcommunications of the uplink information, for example, to enablereceiving accurate rendering information for presentment. For example,frequent updates (e.g., transmissions of the uplink information) may beneeded to provide accurate information about the location of the vehicleand the vehicle-surrounding information to the cloud XR entity.According to one or more aspects, the cloud XR entity may have thecapability to perform pre-fetching and/or compression of information asappropriate. For example, based on the path plan, the cloud XR entitymay pre-fetch XR information related to landmarks that a user may seewhile traveling the route. In some examples, the cloud XR entity mayalso encode and/or compress the rendering information to reduce theamount of information that is transmitted over the air (OTA).Additionally, by enabling the cloud XR entity to generate the XRinformation, one or more aspects disclosed herein facilitate reducingthe computation load of the vehicle UE for displaying the XRinformation. For example, the cloud XR entity may generate the XRinformation instead of the vehicle UE employing static orlocal-processing-based mechanism to generate the XR information.

In some examples, a vehicle XR session may be associated with one ormore XR services, such as navigation services, landmark services,interactivity services, transaction-enabling services, etc. Thenavigation services may enable the displaying of XR information relatedto navigation. The landmark services may enable the displaying of XRinformation related to landmark identification. The interactivityservices may enable the displaying of XR information including one ormore interactive objects. The transaction-enabling services may enablethe displaying of XR information related to performing a transactionbased on an interactive object.

In some examples, when the cloud XR entity receives uplink information,the cloud XR entity may generate the XR information based on the one ormore XR services. For example, based on the uplink information, thecloud XR entity may identify landmarks, opportunities for userinteraction, and/or opportunities for performing a transaction. In suchexamples, the cloud XR entity may generate the rendering information toinclude XR information associated with the respective services.

In some examples, the cloud XR entity may provide granular control of XRservices supported by the vehicle XR session. For example, a vehicle XRsession may be subscription-based and associated with a subscriptionlevel. A subscription level may be associated with a quantity of userstreams that may be associated with a vehicle XR session. For example, afirst subscription level may permit only driver stream, a secondsubscription level may permit only a passenger stream, a thirdsubscription level may permit a driver stream and a passenger stream,and a fourth subscription level may permit any number and combination ofstreams. In some examples, a subscription level may be associated with alevel of XR interactivity. For example, based on the subscription level,the cloud XR entity may generate XR information including differenttypes of interactive objects. In some examples, the subscription levelmay be associated with which services are enabled and/or disabled. Forexample, one subscription level may include navigation services andlandmark services, while another subscription level may includenavigation services, landmark services, interactivity services, andtransaction-enabling services, etc. Thus, according to one or moreexamples, different subscription levels may result in different XRinformation being presented to users. In some examples, the subscriptionlevel may additionally, or alternatively, determine what kind ofservices can be presented to the user. For example, at some subscriptionlevels, a high priority service user, e.g., a police officer, agovernment official, etc., may be presented with landmark services orinteractive services from all surrounding buildings/locations, whileusers who are not high priority service users (e.g., “normal” users),may be presented with only services from commercial buildings/locations.

When establishing the vehicle XR session with the vehicle UE, the cloudXR entity may authorize a supported session level based on thesubscription level. The supported session level may indicate which XRservices are enabled and/or disabled per vehicle XR session and provideXR information accordingly. In some examples, the supported sessionlevel may be based on a Quality of Service (QoS) information and/orQuality of Experience (QoE) information. For example, the cloud XRentity may perform rendering adaptation to provide a satisfactory userexperience. The rendering adaptation may be based on QoE metrics and/orQoS support information provided by the vehicle UE. For example, whencommunications between the vehicle UE and the cloud XR entity aredelayed, packet retransmission is being observed, and/or the data rateis lower than allowed, the cloud XR entity may perform renderingadaptation to adjust the XR information being generated and provided tothe vehicle UE. For example, when the QoE metrics and/or the QoS supportinformation indicates reduced communication capabilities, the cloud XRentity may prioritize XR information associated with a driver stream andmay deprioritize XR information associated with passenger streams. Inthis manner, the cloud XR entity may provide a satisfactory userexperience to the driver, which may be of higher priority than providinga satisfactory user experience to the passengers, for example.

In some examples, the vehicle XR session may be associated with multipleusers. For example, the vehicle XR session may include a first userstream associated with a first user (e.g., a driver) and a second userstream associated with a second user (e.g., a passenger). In suchexamples, the user streams may be associated with the same vehicle. Forexample, the uplink information may include a first user XR componentassociated with the first user, a second user XR component associatedwith the second user, and a vehicle XR component that is shared betweenthe first user stream and the second user stream. The cloud XR entitymay receive the uplink information and the respective components andconsolidate the uplink information so that the rendering informationfacilitates a unified projection to the one or more displays of thevehicle XR system.

The detailed description set forth below in connection with the drawingsdescribes various configurations and does not represent the onlyconfigurations in which the concepts described herein may be practiced.The detailed description includes specific details for the purpose ofproviding a thorough understanding of various concepts. However, theseconcepts may be practiced without these specific details. In someinstances, well known structures and components are shown in blockdiagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems are presented withreference to various apparatus and methods. These apparatus and methodsare described in the following detailed description and illustrated inthe accompanying drawings by various blocks, components, circuits,processes, algorithms, etc. (collectively referred to as “elements”).These elements may be implemented using electronic hardware, computersoftware, or any combination thereof. Whether such elements areimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented as a “processing system” thatincludes one or more processors. Examples of processors includemicroprocessors, microcontrollers, graphics processing units (GPUs),central processing units (CPUs), application processors, digital signalprocessors (DSPs), reduced instruction set computing (RISC) processors,systems on a chip (SoC), baseband processors, field programmable gatearrays (FPGAs), programmable logic devices (PLDs), state machines, gatedlogic, discrete hardware circuits, and other suitable hardwareconfigured to perform the various functionality described throughoutthis disclosure. One or more processors in the processing system mayexecute software. Software, whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise,shall be construed broadly to mean instructions, instruction sets, code,code segments, program code, programs, subprograms, software components,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures,functions, or any combination thereof.

Accordingly, in one or more example aspects, implementations, and/or usecases, the functions described may be implemented in hardware, software,or any combination thereof. If implemented in software, the functionsmay be stored on or encoded as one or more instructions or code on acomputer-readable medium. Computer-readable media includes computerstorage media. Storage media may be any available media that can beaccessed by a computer. By way of example, such computer-readable mediacan comprise a random-access memory (RAM), a read-only memory (ROM), anelectrically erasable programmable ROM (EEPROM), optical disk storage,magnetic disk storage, other magnetic storage devices, combinations ofthe types of computer-readable media, or any other medium that can beused to store computer executable code in the form of instructions ordata structures that can be accessed by a computer.

While aspects, implementations, and/or use cases are described in thisapplication by illustration to some examples, additional or differentaspects, implementations and/or use cases may come about in manydifferent arrangements and scenarios. Aspects, implementations, and/oruse cases described herein may be implemented across many differingplatform types, devices, systems, shapes, sizes, and packagingarrangements. For example, aspects, implementations, and/or use casesmay come about via integrated chip implementations and othernon-module-component based devices (e.g., end-user devices, vehicles,communication devices, computing devices, industrial equipment,retail/purchasing devices, medical devices, artificial intelligence(AI)-enabled devices, etc.). While some examples may or may not bespecifically directed to use cases or applications, a wide assortment ofapplicability of described examples may occur. Aspects, implementations,and/or use cases may range a spectrum from chip-level or modularcomponents to non-modular, non-chip-level implementations and further toaggregate, distributed, or original equipment manufacturer (OEM) devicesor systems incorporating one or more techniques herein. In somepractical settings, devices incorporating described aspects and featuresmay also include additional components and features for implementationand practice of claimed and described aspect. For example, transmissionand reception of wireless signals necessarily includes a number ofcomponents for analog and digital purposes (e.g., hardware componentsincluding antenna, RF-chains, power amplifiers, modulators, buffer,processor(s), interleaver, adders/summers, etc.). Techniques describedherein may be practiced in a wide variety of devices, chip-levelcomponents, systems, distributed arrangements, aggregated ordisaggregated components, end-user devices, etc. of varying sizes,shapes, and constitution.

Deployment of communication systems, such as 5G NR systems, may bearranged in multiple manners with various components or constituentparts. In a 5G NR system, or network, a network node, a network entity,a mobility element of a network, a radio access network (RAN) node, acore network node, a network element, or a network equipment, such as abase station (BS), or one or more units (or one or more components)performing base station functionality, may be implemented in anaggregated or disaggregated architecture. For example, a BS (such as aNode B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), atransmit receive point (TRP), or a cell, etc.) may be implemented as anaggregated base station (also known as a standalone BS or a monolithicBS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocolstack that is physically or logically integrated within a single RANnode. A disaggregated base station may be configured to utilize aprotocol stack that is physically or logically distributed among two ormore units (such as one or more central or centralized units (CUs), oneor more distributed units (DUs), or one or more radio units (RUs)). Insome aspects, a CU may be implemented within a RAN node, and one or moreDUs may be co-located with the CU, or alternatively, may begeographically or virtually distributed throughout one or multiple otherRAN nodes. The DUs may be implemented to communicate with one or moreRUs. Each of the CU, DU and RU can be implemented as virtual units,i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), ora virtual radio unit (VRU).

Base station operation or network design may consider aggregationcharacteristics of base station functionality. For example,disaggregated base stations may be utilized in an integrated access andbackhaul (IAB) network, an open radio access network (O-RAN (such as thenetwork configuration sponsored by the O-RAN Alliance)), or avirtualized radio access network (vRAN, also known as a cloud radioaccess network (C-RAN)). Disaggregation may include distributingfunctionality across two or more units at various physical locations, aswell as distributing functionality for at least one unit virtually,which can enable flexibility in network design. The various units of thedisaggregated base station, or disaggregated RAN architecture, can beconfigured for wired or wireless communication with at least one otherunit.

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network 100. The wireless communications system(also referred to as a wireless wide area network (WWAN)) includes basestations 102, UEs 104, an Evolved Packet Core (EPC) (e.g., an EPC 160),and another core network 190 (e.g., a 5G Core (5GC)). The base stations102 may include macrocells (high power cellular base station) and/orsmall cells (low power cellular base station). The macrocells includebase stations. The small cells include femtocells, picocells, andmicrocells.

The base stations 102 configured for 4G LTE (collectively referred to asEvolved Universal Mobile Telecommunications System (UMTS) TerrestrialRadio Access Network (E-UTRAN)) may interface with the EPC 160 throughfirst backhaul links 132 (e.g., S1 interface). The base stations 102configured for 5G NR (collectively referred to as Next Generation RAN(NG-RAN)) may interface with the core network 190 through secondbackhaul links 184. In addition to other functions, the base stations102 may perform one or more of the following functions: transfer of userdata, radio channel ciphering and deciphering, integrity protection,header compression, mobility control functions (e.g., handover, dualconnectivity), inter-cell interference coordination, connection setupand release, load balancing, distribution for non-access stratum (NAS)messages, NAS node selection, synchronization, radio access network(RAN) sharing, multimedia broadcast multicast service (MBMS), subscriberand equipment trace, RAN information management (RIM), paging,positioning, and delivery of warning messages. The base stations 102 maycommunicate directly or indirectly (e.g., through the EPC 160 or thecore network 190) with each other over third backhaul links 134 (e.g.,an X2 interface). The first backhaul links 132, the second backhaullinks 184 (e.g., an Xn interface), and the third backhaul links 134 maybe wired or wireless.

In some aspects, a base station (e.g., one of the base stations 102 orone of base stations 180) may be referred to as a RAN and may includeaggregated or disaggregated components. As an example of a disaggregatedRAN, a base station may include a central unit (CU) (e.g. a CU 106), oneor more distributed units (DU) (e.g., a DU 105), and/or one or moreremote units (RU) (e.g., an RU 109), as illustrated in FIG. 1 . A RANmay be disaggregated with a split between the RU 109 and an aggregatedCU/DU. A RAN may be disaggregated with a split between the CU 106, theDU 105, and the RU 109. A RAN may be disaggregated with a split betweenthe CU 106 and an aggregated DU/RU. The CU 106 and the one or more DUsmay be connected via an F1 interface. A DU 105 and an RU 109 may beconnected via a fronthaul interface. A connection between the CU 106 anda DU 105 may be referred to as a midhaul, and a connection between a DU105 and the RU 109 may be referred to as a fronthaul. The connectionbetween the CU 106 and the core network 190 may be referred to as thebackhaul.

The RAN may be based on a functional split between various components ofthe RAN, e.g., between the CU 106, the DU 105, or the RU 109. The CU 106may be configured to perform one or more aspects of a wirelesscommunication protocol, e.g., handling one or more layers of a protocolstack, and the one or more DUs may be configured to handle other aspectsof the wireless communication protocol, e.g., other layers of theprotocol stack. In different implementations, the split between thelayers handled by the CU and the layers handled by the DU may occur atdifferent layers of a protocol stack. As one, non-limiting example, a DU105 may provide a logical node to host a radio link control (RLC) layer,a medium access control (MAC) layer, and at least a portion of aphysical (PHY) layer based on the functional split. An RU may provide alogical node configured to host at least a portion of the PHY layer andradio frequency (RF) processing. The CU 106 may host higher layerfunctions, e.g., above the RLC layer, such as a service data adaptationprotocol (SDAP) layer, a packet data convergence protocol (PDCP) layer,and/or an upper layer. In other implementations, the split between thelayer functions provided by the CU, the DU, or the RU may be different.

An access network may include one or more integrated access and backhaul(IAB) nodes (e.g., the IAB nodes 111) that exchange wirelesscommunication with a UE (e.g., one of the UEs 104) or another IAB nodeto provide access and backhaul to a core network. In an IAB network ofmultiple IAB nodes, an anchor node may be referred to as an IAB donor.The IAB donor may be a base station (e.g., one of the base stations 102or one of the base stations 180) that provides access to the corenetwork 190 or the EPC 160 and/or control to one or more of the IABnodes 111. The IAB donor may include a CU 106 and a DU 105. The IABnodes 111 may include a DU 105 and a mobile termination (MT). The DU 105of an IAB node may operate as a parent node, and the MT may operate as achild node.

As described above, deployment of communication systems, such as 5G newradio (NR) systems, may be arranged in multiple manners with variouscomponents or constituent parts. In a 5G NR system, or network, anetwork node, a network entity, a mobility element of a network, a radioaccess network (RAN) node, a core network node, a network element, or anetwork equipment, such as a base station (BS), or one or more units (orone or more components) performing base station functionality, may beimplemented in an aggregated or disaggregated architecture. For example,a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, accesspoint (AP), a transmit receive point (TRP), or a cell, etc.) may beimplemented as an aggregated base station (also known as a standalone BSor a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocolstack that is physically or logically integrated within a single RANnode. A disaggregated base station may be configured to utilize aprotocol stack that is physically or logically distributed among two ormore units (such as one or more central or centralized units (CUs), oneor more distributed units (DUs), or one or more radio units (RUs)). Insome aspects, a CU may be implemented within a RAN node, and one or moreDUs may be co-located with the CU, or alternatively, may begeographically or virtually distributed throughout one or multiple otherRAN nodes. The DUs may be implemented to communicate with one or moreRUs. Each of the CU, DU and RU also can be implemented as virtual units,i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), ora virtual radio unit (VRU).

Base station-type operation or network design may consider aggregationcharacteristics of base station functionality. For example,disaggregated base stations may be utilized in an integrated access andbackhaul (IAB) network, an open radio access network (O-RAN (such as thenetwork configuration sponsored by the O-RAN Alliance)), or avirtualized radio access network (vRAN, also known as a cloud radioaccess network (C-RAN)). Disaggregation may include distributingfunctionality across two or more units at various physical locations, aswell as distributing functionality for at least one unit virtually,which can enable flexibility in network design. The various units of thedisaggregated base station, or disaggregated RAN architecture, can beconfigured for wired or wireless communication with at least one otherunit.

As an example, FIG. 4 shows a diagram illustrating architecture of anexample disaggregated base station 400. The disaggregated base station400 architecture may include one or more CUs (e.g., a CU 410) that cancommunicate directly with a core network 420 via a backhaul link, orindirectly with the core network 420 through one or more disaggregatedbase station units (such as a Near-Real Time (Near-RT) RAN IntelligentController (RIC) (e.g., a Near-RT RIC 425) via an E2 link, or a Non-RealTime (Non-RT) RIC (e.g. a Non-RT RIC 415) associated with a ServiceManagement and Orchestration (SMO) Framework (e.g., an SMO Framework405), or both). The CU 410 (e.g., the CU 106 of FIG. 1 ) may communicatewith one or more DUs (e.g., a DU 430) via respective midhaul links, suchas an F1 interface. A DU 430 (e.g., the DU 105 of FIG. 1 ) maycommunicate with one or more RUs (e.g., an RU 440) via respectivefronthaul links. An RU 440 (e.g., the RU 109 of FIG. 1 ) may communicatewith respective UEs (e.g., the UEs 104 of FIG. 1 ) via one or more radiofrequency (RF) access links. In some implementations, a UE may besimultaneously served by multiple RUs.

Each of the units, i.e., the CU 410, the DU 430, the RU 440, as well asthe Near-RT RIC 425, the Non-RT RIC 415, and the SMO Framework 405, mayinclude one or more interfaces or be coupled to one or more interfacesconfigured to receive or transmit signals, data, or information(collectively, signals) via a wired or wireless transmission medium.Each of the units, or an associated processor or controller providinginstructions to the communication interfaces of the units, can beconfigured to communicate with one or more of the other units via thetransmission medium. For example, the units can include a wiredinterface configured to receive or transmit signals over a wiredtransmission medium to one or more of the other units. Additionally, theunits can include a wireless interface, which may include a receiver, atransmitter or transceiver (such as a radio frequency (RF) transceiver),configured to receive or transmit signals, or both, over a wirelesstransmission medium to one or more of the other units.

In some aspects, the CU 410 may host one or more higher layer controlfunctions. Such control functions can include radio resource control(RRC), packet data convergence protocol (PDCP), service data adaptationprotocol (SDAP), or the like. Each control function can be implementedwith an interface configured to communicate signals with other controlfunctions hosted by the CU 410. The CU 410 may be configured to handleuser plane functionality (i.e., Central Unit—User Plane (CU-UP)),control plane functionality (i.e., Central Unit—Control Plane (CU-CP)),or a combination thereof. In some implementations, the CU 410 can belogically split into one or more CU-UP units and one or more CU-CPunits. The CU-UP unit can communicate bidirectionally with the CU-CPunit via an interface, such as the E1 interface when implemented in anO-RAN configuration. The CU 410 can be implemented to communicate withthe DU 430, as necessary, for network control and signaling.

The DU 430 may correspond to a logical unit that includes one or morebase station functions to control the operation of one or more RUs. Insome aspects, the DU 430 may host one or more of a radio link control(RLC) layer, a medium access control (MAC) layer, and one or more highphysical (PHY) layers (such as modules for forward error correction(FEC) encoding and decoding, scrambling, modulation and demodulation, orthe like) depending, at least in part, on a functional split, such asthose defined by the 3^(rd) Generation Partnership Project (3GPP). Insome aspects, the DU 430 may further host one or more low PHY layers.Each layer (or module) can be implemented with an interface configuredto communicate signals with other layers (and modules) hosted by the DU430, or with the control functions hosted by the CU 410.

Lower-layer functionality can be implemented by one or more RUs. In somedeployments, an RU 440, controlled by a DU 430, may correspond to alogical node that hosts RF processing functions, or low-PHY layerfunctions (such as performing fast Fourier transform (FFT), inverse FFT(iFFT), digital beamforming, physical random access channel (PRACH)extraction and filtering, or the like), or both, based at least in parton the functional split, such as a lower layer functional split. In suchan architecture, the RU(s) can be implemented to handle over the air(OTA) communication with one or more of the UEs 104. In someimplementations, real-time and non-real-time aspects of control and userplane communication with the RU(s) can be controlled by thecorresponding DU. In some scenarios, this configuration can enable theDU(s) and the CU 410 to be implemented in a cloud-based RANarchitecture, such as a vRAN architecture.

The SMO Framework 405 may be configured to support RAN deployment andprovisioning of non-virtualized and virtualized network elements. Fornon-virtualized network elements, the SMO Framework 405 may beconfigured to support the deployment of dedicated physical resources forRAN coverage requirements which may be managed via an operations andmaintenance interface (such as an O1 interface). For virtualized networkelements, the SMO Framework 405 may be configured to interact with acloud computing platform (such as an open cloud 490 (O-Cloud)) toperform network element life cycle management (such as to instantiatevirtualized network elements) via a cloud computing platform interface(such as an O2 interface). Such virtualized network elements caninclude, but are not limited to, the CU 410, the DU 430, the RU 440 andthe Near-RT RIC 425. In some implementations, the SMO Framework 405 cancommunicate with a hardware aspect of a 4G RAN, such as an open eNB(O-eNB) (e.g., an O-eNB 411), via an O1 interface. Additionally, in someimplementations, the SMO Framework 405 can communicate directly with oneor more RUs via an O1 interface. The SMO Framework 405 also may includea Non-RT RIC 415 configured to support functionality of the SMOFramework 405.

The Non-RT RIC 415 may be configured to include a logical function thatenables non-real-time control and optimization of RAN elements andresources, Artificial Intelligence/Machine Learning (AI/ML) workflowsincluding model training and updates, or policy-based guidance ofapplications/features in the Near-RT RIC 425. The Non-RT RIC 415 may becoupled to or communicate with (such as via an A1 interface) the Near-RTRIC 425. The Near-RT RIC 425 may be configured to include a logicalfunction that enables near-real-time control and optimization of RANelements and resources via data collection and actions over an interface(such as via an E2 interface) connecting one or more CUs, one or moreDUs, or both, as well as an O-eNB, with the Near-RT RIC 425.

In some implementations, to generate AI/ML models to be deployed in theNear-RT RIC 425, the Non-RT RIC 415 may receive parameters or externalenrichment information from external servers. Such information may beutilized by the Near-RT RIC 425 and may be received at the SMO Framework405 or the Non-RT RIC 415 from non-network data sources or from networkfunctions. In some examples, the Non-RT RIC 415 or the Near-RT RIC 425may be configured to tune RAN behavior or performance. For example, theNon-RT RIC 415 may monitor long-term trends and patterns for performanceand employ AI/ML models to perform corrective actions through the SMOFramework 405 (such as reconfiguration via O1) or via creation of RANmanagement policies (such as A1 policies).

Referring again to FIG. 1 , the base stations 102 may wirelesslycommunicate with the UEs 104. Each of the base stations 102 may providecommunication coverage for a respective geographic coverage area (e.g.,a coverage area 110). There may be overlapping geographic coverageareas. For example, a small cell 102′ may have a coverage area 110′ thatoverlaps the coverage area 110 of one or more of the base stations 102(e.g., one or more macro base stations). A network that includes bothsmall cell and macrocells may be known as a heterogeneous network. Aheterogeneous network may also include Home Evolved Node Bs (eNBs)(HeNBs), which may provide service to a restricted group known as aclosed subscriber group (CSG). The communication links 120 between thebase stations 102 and the UEs 104 may include uplink (UL) (also referredto as reverse link) transmissions from a UE to a base station and/ordownlink (DL) (also referred to as forward link) transmissions from abase station to a UE. The communication links 120 may use multiple-inputand multiple-output (MIMO) antenna technology, including spatialmultiplexing, beamforming, and/or transmit diversity. The communicationlinks may be through one or more carriers. The base stations 102/UEs 104may use spectrum up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100MHz, 400 MHz, etc.) bandwidth per carrier allocated in a carrieraggregation of up to a total of Yx MHz (x component carriers) used fortransmission in each direction. The carriers may or may not be adjacentto each other. Allocation of carriers may be asymmetric with respect toDL and UL (e.g., more or fewer carriers may be allocated for DL than forUL). The component carriers may include a primary component carrier andone or more secondary component carriers. A primary component carriermay be referred to as a primary cell (PCell) and a secondary componentcarrier may be referred to as a secondary cell (SCell).

Some of the UEs 104 may communicate with each other usingdevice-to-device (D2D) communication link (e.g., a D2D communicationlink 158). The D2D communication link 158 may use the DL/UL WWANspectrum. The D2D communication link 158 may use one or more sidelinkchannels, such as a physical sidelink broadcast channel (PSBCH), aphysical sidelink discovery channel (PSDCH), a physical sidelink sharedchannel (PSSCH), and a physical sidelink control channel (PSCCH). D2Dcommunication may be through a variety of wireless D2D communicationssystems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based onthe Institute of Electrical and Electronics Engineers (IEEE) 802.11standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi accesspoint (AP) 150 in communication with Wi-Fi stations (STAs) (e.g., STAs152) via communication links 154, e.g., in a 5 GHz unlicensed frequencyspectrum or the like. When communicating in an unlicensed frequencyspectrum, the STAs 152/AP 150 may perform a clear channel assessment(CCA) prior to communicating in order to determine whether the channelis available.

The small cell 102′ may operate in a licensed and/or an unlicensedfrequency spectrum. When operating in an unlicensed frequency spectrum,the small cell 102′ may employ NR and use the same unlicensed frequencyspectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. Thesmall cell 102′, employing NR in an unlicensed frequency spectrum, mayboost coverage to and/or increase capacity of the access network.

The electromagnetic spectrum is often subdivided, based onfrequency/wavelength, into various classes, bands, channels, etc. In 5GNR, two initial operating bands have been identified as frequency rangedesignations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz).Although a portion of FR1 is greater than 6 GHz, FR1 is often referredto (interchangeably) as a “sub-6 GHz” band in various documents andarticles. A similar nomenclature issue sometimes occurs with regard toFR2, which is often referred to (interchangeably) as a “millimeter wave”band in documents and articles, despite being different from theextremely high frequency (EHF) band (30 GHz-300 GHz) which is identifiedby the International Telecommunications Union (ITU) as a “millimeterwave” band.

The frequencies between FR1 and FR2 are often referred to as mid-bandfrequencies. Recent 5G NR studies have identified an operating band forthese mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1characteristics and/or FR2 characteristics, and thus may effectivelyextend features of FR1 and/or FR2 into mid-band frequencies. Inaddition, higher frequency bands are currently being explored to extend5G NR operation beyond 52.6 GHz. For example, three higher operatingbands have been identified as frequency range designations FR2-2 (52.6GHz-71 GHz), FR4 (71 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Eachof these higher frequency bands falls within the EHF band.

With the above aspects in mind, unless specifically stated otherwise,the term “sub-6 GHz” or the like if used herein may broadly representfrequencies that may be less than 6 GHz, may be within FR1, or mayinclude mid-band frequencies. Further, unless specifically statedotherwise, the term “millimeter wave” or the like if used herein maybroadly represent frequencies that may include mid-band frequencies, maybe within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.

A base station, whether a small cell 102′ or a large cell (e.g., a macrobase station), may include and/or be referred to as an eNB, gNodeB(gNB), or another type of base station. Some base stations, such as agNB (e.g., one of the base stations 180) may operate in a traditionalsub 6 GHz spectrum, in millimeter wave frequencies, and/or nearmillimeter wave frequencies in communication with the UEs 104. When thegNB operates in millimeter wave or near millimeter wave frequencies, thegNB may be referred to as a millimeter wave base station. The millimeterwave base station may utilize beamforming 182 with one or more of theUEs 104 to compensate for path loss and short range. The base stations180 and the UEs 104 may each include a plurality of antennas, such asantenna elements, antenna panels, and/or antenna arrays to facilitatethe beamforming. Similarly, beamforming may be applied for sidelinkcommunication, e.g., between UEs.

The base stations 180 may transmit a beamformed signal to one or more ofthe UEs 104 in one or more transmit directions 182′. A UE may receivethe beamformed signal from the base station in one or more receivedirections 182″. The UE may also transmit a beamformed signal to thebase station in one or more transmit directions. The base stations 180may receive the beamformed signal from the UE in one or more receivedirections. The base stations 180/the UEs 104 may perform beam trainingto determine the best receive and transmit directions for each of thebase station/the UE. The transmit and receive directions for the basestation may or may not be the same. The transmit and receive directionsfor the UE may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) (e.g., an MME162), other MMEs 164, a Serving Gateway 166, a Multimedia BroadcastMulticast Service (MBMS) Gateway (e.g., an MBMS Gateway 168), aBroadcast Multicast Service Center (BM-SC) (e.g., a BM-SC 170), and aPacket Data Network (PDN) Gateway (e.g., a PDN Gateway 172). The MME 162may be in communication with a Home Subscriber Server (HSS) (e.g., anHSS 174). The MME 162 is the control node that processes the signalingbetween the UEs 104 and the EPC 160. Generally, the MME 162 providesbearer and connection management. All user Internet protocol (IP)packets are transferred through the Serving Gateway 166, which itself isconnected to the PDN Gateway 172. The PDN Gateway 172 provides UE IPaddress allocation as well as other functions. The PDN Gateway 172 andthe BM-SC 170 are connected to IP Services 176. The IP Services 176 mayinclude the Internet, an intranet, an IP Multimedia Subsystem (IMS), aPS Streaming Service, and/or other IP services. The BM-SC 170 mayprovide functions for MBMS user service provisioning and delivery. TheBM-SC 170 may serve as an entry point for content provider MBMStransmission, may be used to authorize and initiate MBMS Bearer Serviceswithin a public land mobile network (PLMN), and may be used to scheduleMBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMStraffic to the base stations 102 belonging to a Multicast BroadcastSingle Frequency Network (MBSFN) area broadcasting a particular service,and may be responsible for session management (start/stop) and forcollecting eMBMS related charging information.

The core network 190 may include an Access and Mobility ManagementFunction (AMF) (e.g., an AMF 192), other AMFs 193, a Session ManagementFunction (SMF) (e.g., an SMF 194), and a User Plane Function (UPF)(e.g., a UPF 195). The AMF 192 may be in communication with a UnifiedData Management (UDM) (e.g., a UDM 196). The AMF 192 is the control nodethat processes the signaling between the UEs 104 and the core network190. Generally, the AMF 192 provides QoS flow and session management.All user Internet protocol (IP) packets are transferred through the UPF195. The UPF 195 provides UE IP address allocation as well as otherfunctions. The UPF 195 is connected to IP Services 197. The IP Services197 may include the Internet, an intranet, an IP Multimedia Subsystem(IMS), a Packet Switch (PS) Streaming Service, and/or other IP services.

The base station may include and/or be referred to as a gNB, Node B,eNB, an access point, a base transceiver station, a radio base station,a radio transceiver, a transceiver function, a basic service set (BSS),an extended service set (ESS), a transmit receive point (TRP), or someother suitable terminology. The base stations 102 provide an accesspoint to the EPC 160 or the core network 190 for the UEs 104. Examplesof the UEs 104 include a cellular phone, a smart phone, a sessioninitiation protocol (SIP) phone, a laptop, a personal digital assistant(PDA), a satellite radio, a global positioning system, a multimediadevice, a video device, a digital audio player (e.g., MP3 player), acamera, a game console, a tablet, a smart device, a wearable device, avehicle, an electric meter, a gas pump, a large or small kitchenappliance, a healthcare device, an implant, a sensor/actuator, adisplay, or any other similar functioning device. Some of the UEs 104may be referred to as IoT devices (e.g., parking meter, gas pump,toaster, vehicles, heart monitor, etc.). The UEs 104 may also bereferred to as a station, a mobile station, a subscriber station, amobile unit, a subscriber unit, a wireless unit, a remote unit, a mobiledevice, a wireless device, a wireless communications device, a remotedevice, a mobile subscriber station, an access terminal, a mobileterminal, a wireless terminal, a remote terminal, a handset, a useragent, a mobile client, a client, or some other suitable terminology. Insome scenarios, the term UE may also apply to one or more companiondevices such as in a device constellation arrangement. One or more ofthese devices may collectively access the network and/or individuallyaccess the network.

Referring again to FIG. 1 , in certain aspects, a device incommunication with a network entity, such as one of the UEs 104 incommunication with one of the base stations 102 or a component of a basestation (e.g., a CU 106, a DU 105, and/or an RU 109), may be configuredto manage one or more aspects of wireless communication. For example,one or more of the UEs 104 (e.g., a vehicle UE) may include a vehicle XRcomponent 198 configured to facilitate an XR user experience associatedwith a vehicle. In certain aspects, the vehicle XR component 198 may beconfigured to transmit a request for a vehicle XR session, the vehicleXR session being based on a first user XR stream including a vehicle XRcomponent associated with a vehicle and a first user XR componentassociated with a first user, the first user having an association withthe vehicle. The example vehicle XR component 198 may also be configuredto transmit uplink information associated with the first user XR stream.Additionally, the example vehicle XR component 198 may be configured toreceive rendering information associated with the first user XR stream,the rendering information being based on the uplink information.

In another configuration, a network entity, such as one of the basestations 102 or a component of a base station (e.g., a CU 106, a DU 105,and/or an RU 109), or an aerial device 103, may be configured to manageor more aspects of wireless communication. For example, one or more ofthe base stations 102 may include a vehicle-to-cloud XR networkcomponent 199 configured to facilitate an XR user experience associatedwith a vehicle. In certain aspects, the vehicle-to-cloud XR networkcomponent 199 may be configured to obtain a request for a vehicle XRsession. The vehicle-to-cloud XR network component 199 may also beconfigured to authorize the vehicle XR session, the vehicle XR sessionbeing based on a first user XR stream including a vehicle XR componentassociated with a vehicle and a first user XR component associated witha first user, the first user having an association with the vehicle. Theexample vehicle-to-cloud XR network component 199 may also be configuredto obtain uplink information associated with the first user XR stream.Additionally, the example vehicle-to-cloud XR network component 199 maybe configured to output rendering information associated with the firstuser XR stream, the rendering information being based on the uplinkinformation. In some examples, the vehicle-to-cloud XR network component199 may be configured to additionally, or alternatively, provideadditional information related to the vehicle XR session associated withthe vehicle, such as location information of the vehicle, sensinginformation about the surrounding environment of the vehicleenvironment, etc.

In another configuration, a network entity, such as the EPC 160 and/orthe core network 190 or a component of the network entity, may beconfigured to manage one or more aspects of wireless communication. Forexample, the EPC 160 and/or the core network 190 may include avehicle-to-cloud XR component 191 configured to facilitate an XR userexperience associated with a vehicle. The vehicle-to-cloud XR component191 may be a new logical entity in the EPC 160 or the core network 190,or new functions distributed in existing entities inside the EPC 160 orthe core network 190, such as the AMF 192, the SMF 194, the UPF 195, orthe MME 162, the Serving Gateway 166, the PDN Gateway 172, the MBMS GW168, and/or the BM-SC 170. In certain aspects, the vehicle-to-cloud XRcomponent 191 may be configured to obtain a request for a vehicle XRsession. The vehicle-to-cloud XR component 191 may also be configured toauthorize the vehicle XR session, the vehicle XR session being based ona first user XR stream including a vehicle XR component associated witha vehicle and a first user XR component associated with a first user,the first user having an association with the vehicle. The examplevehicle-to-cloud XR component 191 may also be configured to obtainuplink information associated with the first user XR stream.Additionally, the example vehicle-to-cloud XR component 191 may beconfigured to output rendering information associated with the firstuser XR stream, the rendering information being based on the uplinkinformation. The vehicle-to-cloud XR component 191 may be configured toprovide the necessary handling of the connection request for the vehicleXR session, e.g., establishing the required protocol data unit (PDU)sessions, selecting the appropriate UPF, authorizing the session basedon subscription information, setting the proper QoS levels and chargingrecords, etc. In another example, the vehicle-to-cloud XR component 191may be realized outside of the EPC 160 or the core network 190, forexample, beyond the PDN Gateway 172 or the UPF 195.

The aspects presented herein may enable a UE to provide a XR userexperience in a vehicle. For example, aspects presented herein mayenable network-based operation support to determine information tosupport the XR user experience in the vehicle, which may facilitateimproving communication performance, for example, by reducingcomputation load at the vehicle.

Although the following description provides examples directed to 5G NR,the concepts described herein may be applicable to other similar areas,such as LTE, LTE-A, CDMA, GSM, 5G-Advanced, 6G, and/or other wirelesstechnologies.

FIG. 2A is a diagram 200 illustrating an example of a first subframewithin a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating anexample of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250illustrating an example of a second subframe within a 5G NR framestructure. FIG. 2D is a diagram 280 illustrating an example of ULchannels within a 5G NR subframe. The 5G NR frame structure may befrequency division duplexed (FDD) in which for a particular set ofsubcarriers (carrier system bandwidth), subframes within the set ofsubcarriers are dedicated for either DL or UL, or may be time divisionduplexed (TDD) in which for a particular set of subcarriers (carriersystem bandwidth), subframes within the set of subcarriers are dedicatedfor both DL and UL. In the examples provided by FIGS. 2A, 2C, the 5G NRframe structure is assumed to be TDD, with subframe 4 being configuredwith slot format 28 (with mostly DL), where D is DL, U is UL, and F isflexible for use between DL/UL, and subframe 3 being configured withslot format 1 (with all UL). While subframes 3, 4 are shown with slotformats 1, 28, respectively, any particular subframe may be configuredwith any of the various available slot formats 0-61. Slot formats 0, 1are all DL, UL, respectively. Other slot formats 2-61 include a mix ofDL, UL, and flexible symbols. UEs are configured with the slot format(dynamically through DL control information (DCI), orsemi-statically/statically through radio resource control (RRC)signaling) through a received slot format indicator (SFI). Note that thedescription infra applies also to a 5G NR frame structure that is TDD.

FIGS. 2A-2D illustrate a frame structure, and the aspects of the presentdisclosure may be applicable to other wireless communicationtechnologies, which may have a different frame structure and/ordifferent channels. A frame (10 ms) may be divided into 10 equally sizedsubframes (1 ms). Each subframe may include one or more time slots.Subframes may also include mini-slots, which may include 7, 4, or 2symbols. Each slot may include 14 or 12 symbols, depending on whetherthe cyclic prefix (CP) is normal or extended. For normal CP, each slotmay include 14 symbols, and for extended CP, each slot may include 12symbols. The symbols on DL may be CP orthogonal frequency divisionmultiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDMsymbols (for high throughput scenarios) or discrete Fourier transform(DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as singlecarrier frequency-division multiple access (SC-FDMA) symbols) (for powerlimited scenarios; limited to a single stream transmission). The numberof slots within a subframe is based on the CP and the numerology. Thenumerology defines the subcarrier spacing (SCS) and, effectively, thesymbol length/duration, which is equal to 1/SCS.

SCS μ Δf = 2^(μ) · 15[kHz] Cyclic prefix 0 15 Normal 1 30 Normal 2 60Normal, Extended 3 120 Normal 4 240 Normal

For normal CP (14 symbols/slot), different numerologies μ0 to 4 allowfor 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extendedCP, the numerology 2 allows for 4 slots per subframe. Accordingly, fornormal CP and numerology μ, there are 14 symbols/slot and 2^(μ)slots/subframe. As shown in Table 1, the subcarrier spacing may be equalto 2^(μ_l *)15 kHz, where μ is the numerology 0 to 4. As such, thenumerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4has a subcarrier spacing of 240 kHz. The symbol length/duration isinversely related to the subcarrier spacing. FIGS. 2A-2D provide anexample of normal CP with 14 symbols per slot and numerology μ=2 with 4slots per subframe. The slot duration is 0.25 ms, the subcarrier spacingis 60 kHz, and the symbol duration is approximately 16.67 μs. Within aset of frames, there may be one or more different bandwidth parts (BWPs)(see FIG. 2B) that are frequency division multiplexed. Each BWP may havea particular numerology and CP (normal or extended).

A resource grid may be used to represent the frame structure. Each timeslot includes a resource block (RB) (also referred to as physical RBs(PRBs)) that extends 12 consecutive subcarriers. The resource grid isdivided into multiple resource elements (REs). The number of bitscarried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot)signals (RS) for the UE. The RS may include demodulation RS (DM-RS)(indicated as R for one particular configuration, but other DM-RSconfigurations are possible) and channel state information referencesignals (CSI-RS) for channel estimation at the UE. The RS may alsoinclude beam measurement RS (BRS), beam refinement RS (BRRS), and phasetracking RS (PT-RS).

FIG. 2B illustrates an example of various DL channels within a subframeof a frame. The physical downlink control channel (PDCCH) carries DCIwithin one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or16 CCEs), each CCE including six RE groups (REGs), each REG including 12consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP maybe referred to as a control resource set (CORESET). A UE is configuredto monitor PDCCH candidates in a PDCCH search space (e.g., common searchspace, UE-specific search space) during PDCCH monitoring occasions onthe CORESET, where the PDCCH candidates have different DCI formats anddifferent aggregation levels. Additional BWPs may be located at greaterand/or lower frequencies across the channel bandwidth. A primarysynchronization signal (PSS) may be within symbol 2 of particularsubframes of a frame. The PSS is used by a UE to determinesubframe/symbol timing and a physical layer identity. A secondarysynchronization signal (SSS) may be within symbol 4 of particularsubframes of a frame. The SSS is used by a UE to determine a physicallayer cell identity group number and radio frame timing. Based on thephysical layer identity and the physical layer cell identity groupnumber, the UE can determine a physical cell identifier (PCI). Based onthe PCI, the UE can determine the locations of the DM-RS. The physicalbroadcast channel (PBCH), which carries a master information block(MIB), may be logically grouped with the PSS and SSS to form asynchronization signal (SS)/PBCH block (also referred to as SS block(SSB)). The MIB provides a number of RBs in the system bandwidth and asystem frame number (SFN). The physical downlink shared channel (PDSCH)carries user data, broadcast system information not transmitted throughthe PBCH such as system information blocks (SIBs), and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as Rfor one particular configuration, but other DM-RS configurations arepossible) for channel estimation at the base station. The UE maytransmit DM-RS for the physical uplink control channel (PUCCH) and DM-RSfor the physical uplink shared channel (PUSCH). The PUSCH DM-RS may betransmitted in the first one or two symbols of the PUSCH. The PUCCHDM-RS may be transmitted in different configurations depending onwhether short or long PUCCHs are transmitted and depending on theparticular PUCCH format used. The UE may transmit sounding referencesignals (SRS). The SRS may be transmitted in the last symbol of asubframe. The SRS may have a comb structure, and a UE may transmit SRSon one of the combs. The SRS may be used by a base station for channelquality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframeof a frame. The PUCCH may be located as indicated in one configuration.The PUCCH carries uplink control information (UCI), such as schedulingrequests, a channel quality indicator (CQI), a precoding matrixindicator (PMI), a rank indicator (RI), and hybrid automatic repeatrequest (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one ormore HARQ ACK bits indicating one or more ACK and/or negative ACK(NACK)). The PUSCH carries data, and may additionally be used to carry abuffer status report (BSR), a power headroom report (PHR), and/or UCI.

FIG. 3 is a block diagram that illustrates an example of a firstwireless device that is configured to exchange wireless communicationwith a second wireless device. In the illustrated example of FIG. 3 ,the first wireless device may include a base station 310, the secondwireless device may include a UE 350, and the base station 310 may be incommunication with the UE 350 in an access network. As shown in FIG. 3 ,the base station 310 includes a transmit processor (TX processor 316), atransmitter 318Tx, a receiver 318Rx, antennas 320, a receive processor(RX processor 370), a channel estimator 374, a controller/processor 375,and memory 376. The example UE 350 includes antennas 352, a transmitter354Tx, a receiver 354Rx, an RX processor 356, a channel estimator 358, acontroller/processor 359, memory 360, and a TX processor 368. In otherexamples, the base station 310 and/or the UE 350 may include additionalor alternative components.

In the DL, Internet protocol (IP) packets may be provided to thecontroller/processor 375. The controller/processor 375 implements layer3 and layer 2 functionality. Layer 3 includes a radio resource control(RRC) layer, and layer 2 includes a service data adaptation protocol(SDAP) layer, a packet data convergence protocol (PDCP) layer, a radiolink control (RLC) layer, and a medium access control (MAC) layer. Thecontroller/processor 375 provides RRC layer functionality associatedwith broadcasting of system information (e.g., MIB, SIBs), RRCconnection control (e.g., RRC connection paging, RRC connectionestablishment, RRC connection modification, and RRC connection release),inter radio access technology (RAT) mobility, and measurementconfiguration for UE measurement reporting; PDCP layer functionalityassociated with header compression/decompression, security (ciphering,deciphering, integrity protection, integrity verification), and handoversupport functions; RLC layer functionality associated with the transferof upper layer protocol data units (PDUs), error correction through ARQ,concatenation, segmentation, and reassembly of RLC service data units(SDUs), re-segmentation of RLC data PDUs, and reordering of RLC dataPDUs; and MAC layer functionality associated with mapping betweenlogical channels and transport channels, multiplexing of MAC SDUs ontotransport blocks (TBs), demultiplexing of MAC SDUs from TBs, schedulinginformation reporting, error correction through HARQ, priority handling,and logical channel prioritization.

The TX processor 316 and the RX processor 370 implement layer 1functionality associated with various signal processing functions. Layer1, which includes a physical (PHY) layer, may include error detection onthe transport channels, forward error correction (FEC) coding/decodingof the transport channels, interleaving, rate matching, mapping ontophysical channels, modulation/demodulation of physical channels, andMIMO antenna processing. The TX processor 316 handles mapping to signalconstellations based on various modulation schemes (e.g., binaryphase-shift keying (BPSK), quadrature phase-shift keying (QPSK),M-phase-shift keying (M-PSK), M-quadrature amplitude modulation(M-QAM)). The coded and modulated symbols may then be split intoparallel streams. Each stream may then be mapped to an OFDM subcarrier,multiplexed with a reference signal (e.g., pilot) in the time and/orfrequency domain, and then combined together using an Inverse FastFourier Transform (IFFT) to produce a physical channel carrying a timedomain OFDM symbol stream. The OFDM stream is spatially precoded toproduce multiple spatial streams. Channel estimates from the channelestimator 374 may be used to determine the coding and modulation scheme,as well as for spatial processing. The channel estimate may be derivedfrom a reference signal and/or channel condition feedback transmitted bythe UE 350. Each spatial stream may then be provided to a differentantenna of the antennas 320 via a separate transmitter (e.g., thetransmitter 318Tx). Each transmitter 318Tx may modulate a radiofrequency (RF) carrier with a respective spatial stream fortransmission.

At the UE 350, each receiver 354Rx receives a signal through itsrespective antenna of the antennas 352. Each receiver 354Rx recoversinformation modulated onto an RF carrier and provides the information tothe RX processor 356. The TX processor 368 and the RX processor 356implement layer 1 functionality associated with various signalprocessing functions. The RX processor 356 may perform spatialprocessing on the information to recover any spatial streams destinedfor the UE 350. If multiple spatial streams are destined for the UE 350,two or more of the multiple spatial streams may be combined by the RXprocessor 356 into a single OFDM symbol stream. The RX processor 356then converts the OFDM symbol stream from the time-domain to thefrequency domain using a Fast Fourier Transform (FFT). The frequencydomain signal comprises a separate OFDM symbol stream for eachsubcarrier of the OFDM signal. The symbols on each subcarrier, and thereference signal, are recovered and demodulated by determining the mostlikely signal constellation points transmitted by the base station 310.These soft decisions may be based on channel estimates computed by thechannel estimator 358. The soft decisions are then decoded anddeinterleaved to recover the data and control signals that wereoriginally transmitted by the base station 310 on the physical channel.The data and control signals are then provided to thecontroller/processor 359, which implements layer 3 and layer 2functionality.

The controller/processor 359 can be associated with the memory 360 thatstores program codes and data. The memory 360 may be referred to as acomputer-readable medium. In the UL, the controller/processor 359provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, and control signalprocessing to recover IP packets. The controller/processor 359 is alsoresponsible for error detection using an ACK and/or NACK protocol tosupport HARQ operations.

Similar to the functionality described in connection with the DLtransmission by the base station 310, the controller/processor 359provides RRC layer functionality associated with system information(e.g., MIB, SIBs) acquisition, RRC connections, and measurementreporting; PDCP layer functionality associated with headercompression/decompression, and security (ciphering, deciphering,integrity protection, integrity verification); RLC layer functionalityassociated with the transfer of upper layer PDUs, error correctionthrough ARQ, concatenation, segmentation, and reassembly of RLC SDUs,re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; andMAC layer functionality associated with mapping between logical channelsand transport channels, multiplexing of MAC SDUs onto TBs,demultiplexing of MAC SDUs from TBs, scheduling information reporting,error correction through HARQ, priority handling, and logical channelprioritization.

Channel estimates derived by the channel estimator 358 from a referencesignal or feedback transmitted by the base station 310 may be used bythe TX processor 368 to select the appropriate coding and modulationschemes, and to facilitate spatial processing. The spatial streamsgenerated by the TX processor 368 may be provided to different antennaof the antennas 352 via separate transmitters (e.g., the transmitter354Tx). Each transmitter 354Tx may modulate an RF carrier with arespective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a mannersimilar to that described in connection with the receiver function atthe UE 350. Each receiver 318Rx receives a signal through its respectiveantenna of the antennas 320. Each receiver 318Rx recovers informationmodulated onto an RF carrier and provides the information to the RXprocessor 370.

The controller/processor 375 can be associated with the memory 376 thatstores program codes and data. The memory 376 may be referred to as acomputer-readable medium. In the UL, the controller/processor 375provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover IP packets. The controller/processor 375 is also responsiblefor error detection using an ACK and/or NACK protocol to support HARQoperations.

At least one of the TX processor 368, the RX processor 356, and thecontroller/processor 359 may be configured to perform aspects inconnection with the vehicle XR component 198 of FIG. 1 .

At least one of the TX processor 316, the RX processor 370, and thecontroller/processor 375 may be configured to perform aspects inconnection with the vehicle-to-cloud XR network component 199 of FIG. 1.

As described above, XR refers to the reality-virtuality continuumbetween real environments and virtual environments. Extended realitytechnologies can provide virtual content to a user, and/or combine realor physical environments and virtual environments, which may be made upof virtual content or virtual objects, to provide users with XRexperiences. An XR experience may include VR, AR, MR, and/or otherimmersive content. Augmented reality (AR) may merge the real world withvirtual objects to support realistic, intelligent, and personalizedexperiences. Virtual reality (VR) provides a level of immersion, forexample, by creating a sense of physical presence in real or imaginedworlds. Augmented virtuality (AV) merges the virtual world with realworld objects. Mixed reality (MR) merges the real world with the virtualworld to produce new environments and visualizations where physicalobjects and virtual objects can co-exist and interact with each other.Extended reality (XR) includes AR, AV, VR, and MR, and refers to thefull reality-virtuality continuum between real environments and virtualenvironments.

A user may experience XR (e.g., may be provided with an XR experience)via an XR device. Extended reality devices may be of different formfactors and may differ in processing capabilities, power consumption,and/or communication types. One example of an XR device is an HMD. TheHMD may include a display positioned in front of one or both eyes. Thedisplay may stream data, images, and/or other information in front ofthe user's eye(s).

An HMD may include an optical system, such as a display and/or lenses,one or more tracking sensors, one or more cameras, communicationfunctionalities, and an XR engine. The XR engine may perform XR-relatedprocessing and may include one or more GPUs, CPUs, etc. The display ofan HMD may be transparent or not transparent. For example, for an ARapplication, the display may be transparent (or mostly transparent) andAR information may be superimposed onto real life objects. In anotherexample, for a VR application, the display may not be transparent andvirtual information and images may be displayed in front of the user'seyes.

One example application of XR is associated with vehicles. For example,a vehicle may be configured with an XR system that provides avehicle-based XR experience to users of the vehicle. The vehicle mayinclude a terrestrial vehicle, such as a car, a bus, a train, etc., oran airborne/non-terrestrial vehicle, such as a drone, a balloon, aplane, a helicopter, etc. The user of the vehicle may be a human, adevice with artificial intelligence, a communication equipmentsupporting remote access, or a connected controller. The XR system ofthe vehicle may have a different form factor than an HMD, but mayinclude one or more similar components.

FIG. 5 is a diagram illustrating an example vehicle 500 configured witha vehicle XR system, as presented herein. The vehicle 500 of FIG. 5includes a seat for a driver 502, a seat for a first passenger 504, anda seat for a second passenger 506. In the example of FIG. 5 , the driver502 and the first passenger 504 are positioned in a same row (e.g., afront row) and the second passenger 506 is positioned in a different row(e.g., a back row). However, other examples may include additional oralternate configurations for the driver and one or more passengers.

In the example of FIG. 5 , the vehicle 500 is configured with a vehicleXR system, which may also be referred to as a “vehicle XR platform” orby another name. The vehicle XR system facilitates providing vehicle XRto users of the vehicle 500. The vehicle XR system of FIG. 5 includes afirst display 510, one or more sensors 512, and a vehicle UE 514. Thefirst display 510 may include a heads-up display that adds augmentationinformation. The augmentation information may include information thatis superimposed over real world objects via the first display 510. Forexample, the augmentation information may include identifiers oflandmarks, interactive objects, additional information associated with areal world object, etc. The one or more sensors 512 may includecamera(s), GPS sensor(s), radar sensor(s), light detection and ranging(LiDAR) sensor(s), etc. The one or more sensors 512 may be associatedwith an advanced driver assistant system (ADAS) of the vehicle 500and/or may be in-cabin sensors. For example, the in-cabin sensors may beable to provide the pose information of the users of the vehicle, suchas the driver 502, the first passenger 504, and/or the second passenger506. The vehicle UE 514 may provide communication functionalities andXR-based processing.

As an example of a vehicle XR application, a navigation system of thevehicle 500 may enable a user (e.g., the driver 502, the first passenger504, and/or the second passenger 506) to input a desired destination andgenerate a path plan (e.g., a route) to arrive at the desireddestination. The one or more sensors 512 may capture vehicle-surroundinginformation of the area around the vehicle 500. The vehicle UE 514 maythen process the vehicle-surrounding information and generate renderinginformation accordingly. The first display 510 may then display therendering information. For example, the rendering information mayinclude augmentation information that is superimposed on the real worldobjects surrounding the vehicle 500. Examples of real world objectssurrounding the vehicle may include traffic lights, hazard signs, roadsigns, barricades, landmarks, buildings, billboards, etc. Theaugmentation information may include driver assistance information, suchas a current speed of the vehicle 500, a speed limit, gas-related orbattery-related information, upcoming directions, traffic light phasinginformation, information of potential maneuver of the surroundingvehicles and vulnerable road users (VRUs), road conditions, etc.

FIG. 6A depicts a scene 600 in which a heads-up display of a vehiclesuperimposes augmentation information over real world objects and/orrepresentations of real world objects, as presented herein. In theexample of FIG. 6A, the scene 600 includes real world objects, such as atraffic light 602, a hazard sign 604, a directional sign 606, barricades608, and a median 610. The scene 600 also includes augmentationinformation 620 that may be superimposed on the real world objects via adisplay, such as the first display 510 of FIG. 5 . In the example ofFIG. 6A, the augmentation information 620 includes information relatedto the speed of the vehicle, a speed limit, navigation information, etc.

In the examples of FIG. 5 and FIG. 6A, the augmentation information 620is based on what the vehicle UE 514 is able to identify and then presentvia the first display 510. For example, the augmentation information 620may be identified and presented based on a static orlocal-processing-based mechanism. Examples of static orlocal-processing-based mechanisms may be based on pre-configuredinformation stored at the vehicle UE. For example, the vehicle UE may beconfigured with augmentation information corresponding to navigation,such as indicators of speed limits associated with streets or highways.In some such examples, the vehicle UE may identify, based on informationprovided by the one or more sensors of the vehicle XR system, a realworld object, such as a street sign. According to one or more examples,the vehicle UE may then display augmentation information indicating thespeed limit associated with the street based on the identified streetsign.

In some examples, the augmentation information 620 may be generated anddisplayed via the first display 510 regardless of where the driver 502is looking. For example, the driver 502 may be looking out a window 516of the vehicle 500 and unable to see augmentation information displayedvia the first display 510. In such examples, the vehicle UE 514 may beusing resources (e.g., processing resources, memory, etc.) to generateand present the augmentation information 620 with defaultconfigurations. Additionally, in some examples, the augmentationinformation 620 presented in the scene 600 may be limited to whatobjects the vehicle UE 514 is able to identify and/or may be limited tothe information provided by another system of the vehicle, such as thenavigation system.

FIG. 6B depicts a scene 650 including real world objects, as presentedherein. In the example of FIG. 6B, the scene 650 includes real worldobjects, such as a traffic light 652, a median 654, electronicbillboards 656, a bus 658, and a train stop 660.

FIG. 6C depicts a scene 670 including virtual objects superimposed overreal world objects, as presented herein. For example, the scene 670includes augmentation information that may be superimposed on the realworld objects of FIG. 6B that may be presented via a display associatedwith a vehicle XR system, such as the first display 510 of FIG. 5 . Inthe example of FIG. 6C, the augmentation information includes landmarkinformation 671, navigation information 672, and an interactive object674 that is superimposed over the train stop 660.

In some examples, a user (e.g., a driver and/or a passenger) may bepresented with interactive objects with which the user may engage. Insome examples, engaging with the interactive object may provideadditional information about real world objects. For example, in theexample of FIG. 6C, selecting the interactive object 674 may provideadditional information for a related landmark, such as the train stop660. For example, if a user selects the interactive object 674, the usermay be presented with augmentation information 676 that providesinformation related to the train stop 660, such as the name of the trainstop, a distance to the train stop, the next scheduled train arrival,etc.

Aspects disclosed herein facilitate a vehicle XR application thatincludes cloud-based processing. For example, aspects disclosed hereinenable offloading some processing associated with presentingaugmentation information to a cloud XR entity. The cloud XR entity maybe in communication with a vehicle UE of a vehicle XR system, such asthe vehicle UE 514 of FIG. 5 . The cloud XR entity may receiveinformation collected from the vehicle UE 514 via one or more sensors ofthe vehicle XR system, such as the one or more sensors 512. The cloud XRentity may then help determine what rendering information is needed tosupport the vehicle XR application at the vehicle UE 514 and to providea satisfactory user experience (e.g., an XR experience that may beappreciated by the user). For example, the cloud XR entity may have theability to identify real world objects in real-time (or near real-time)based on the information received from the vehicle UE. For example,based on the information received from the vehicle UE, the cloud XRentity may have the ability to identify that an intersection has acoffee shop and provide augmentation information associated with thecoffee shop.

In some aspects, the vehicle UE and the cloud XR entity may establish avehicle XR session. The vehicle XR session may enable communicationassociated with a user stream between the vehicle UE and the cloud XRentity. For example, the user stream may include uplink information thatis provided by the vehicle UE to the cloud XR entity. The user streammay also include downlink information that is provided by the cloud XRentity to the vehicle UE.

The uplink information may include information that is collected by theone or more sensors of the vehicle XR system. The uplink information mayinclude information about the vehicle and information about a user. Forexample, the collected information may include a vehicle XR componentthat includes one or more of vehicle pose information, vehicleinformation, and vehicle-surrounding information. The uplink informationmay also include a user XR component that includes one or more of userpose information and input information. The user pose information mayinclude information relating to a position and/or orientation of theuser in space relative to an XR space. An XR space may represent avirtual coordinate system with an origin that corresponds to a physicallocation. The user pose information may be with respect to the ground(e.g., absolute pose information) and/or with respect to the vehicle(e.g., relative pose information). The input information may includeinformation related to user eye tracking and/or user gestures.

The downlink information from the cloud XR entity to the vehicle UE mayinclude rendering information for presentment at the vehicle. Forexample, the rendering information may include XR information, such asaugmentation information, that the vehicle UE is configured tosuperimpose over real world objects. The vehicle UE may also display theXR information via the one or more displays of the vehicle XR system.

The cloud XR entity may obtain the uplink information and performvirtual-physical fusion of the information to generate the renderinginformation. In one or more aspects, the virtual-physical fusion of theinformation may include identifying real world objects and XRinformation. For example, the cloud XR entity may identify the realworld objects based on the vehicle-surrounding information of thevehicle XR component of the uplink information. The cloud XR entity mayalso generate XR information based on the identified real world objects.In some examples, the cloud XR entity may generate the XR informationbased on information received from additional network entities. Forexample, the cloud XR entity may identify a sports stadium and obtain XRinformation associated with the sports stadium from a network entitythat provides sports-based information. The cloud XR entity may thenprovide the rendering information to the vehicle UE for presentment. Forexample, the vehicle UE may facilitate displaying the renderinginformation via the one or more displays of the vehicle.

Additionally, as XR systems and communication systems evolve and mature,more XR experiences may emerge. For example, rather than a vehicle XRapplication that displays information without taking driver informationinto account, the cloud XR entity could adapt the rendering informationprovided to the vehicle UE based on user pose. In such examples, the XRapplication may present information relevant to a user (e.g., thedriver) as the user moves their head and what the user is seeingchanges. The rendering information provided to the vehicle UE may beadjusted according to the status of the user, or the situation of thevehicle. For example, certain traffic related information may not bepresented to the user when the vehicle is parked. In another example,only driving related XR information may be presented to the driver whenthe vehicle is moving at higher speed.

Additionally, the cloud XR entity may allow passengers to be providedwith an XR experience. For example, the one or more sensors of thevehicle XR system may collect information associated with differentusers (e.g., a driver and one or more passengers). In some suchexamples, the cloud XR entity may have the ability to generate XRinformation for the different users. For example, passengers may bepresented with XR information that is the same or different than thedriver. For example, a driver may be presented with first XR informationthat is related to navigation (e.g., direction, speed, etc.) whilepassengers may be presented with second XR information related tolandmarks. According to one or more examples, the XR informationpresented to the passengers may be shielded from the view of the driver,for example, to avoid distracting the driver.

In some examples, the rendering information provided to the vehicle UEmay include interactive objects with which the user may engage. In someexamples, engaging with the interactive object may provide additionalinformation about real world objects. For example, an interactive objectmay be superimposed above a landmark. In some examples, a user mayengage with (e.g., select) the interactive object to receive informationabout the landmark. In some examples, a user may engage with theinteractive object to perform a transaction. For example, the renderinginformation may include an interactive object that is superimposed abovea coffee shop. In some examples, the user may select the interactiveobject to initiate a coffee purchase at the coffee shop. In someexamples, the input information of the user XR component may includeinformation indicating engagement with the interactive object.

In some examples, the vehicle UE may provide relatively frequentcommunications of the uplink information, for example, to enablereceiving accurate rendering information for presentment. For example,frequent updates (e.g., transmissions of the uplink information) may beneeded to provide accurate information about the location of the vehicleand the vehicle-surrounding information to the cloud XR entity.According to one or more aspects, the cloud XR entity may have thecapability to perform pre-fetching and/or compression of information asappropriate. For example, based on the path plan, the cloud XR entitymay pre-fetch XR information related to landmarks that a user may seewhile traveling the route. In some examples, the cloud XR entity mayalso encode and/or compress the rendering information to reduce theamount of information that is transmitted over the air (OTA).Additionally, by enabling the cloud XR entity to generate the XRinformation, one or more aspects disclosed herein facilitate reducingthe computation load of the vehicle UE for displaying the XRinformation. For example, the cloud XR entity may generate the XRinformation instead of the vehicle UE employing static orlocal-processing-based mechanism to generate the XR information.

In some examples, a vehicle XR session may be associated with one ormore XR services, such as navigation services, landmark services,interactivity services, transaction-enabling services, etc. Thenavigation services may enable the displaying of XR information relatedto navigation. The landmark services may enable the displaying of XRinformation related to landmark identification. The interactivityservices may enable the displaying of XR information including one ormore interactive objects. The transaction-enabling services may enablethe displaying of XR information related to performing a transactionbased on an interactive object.

In some examples, when the cloud XR entity receives uplink information,the cloud XR entity may generate the XR information based on the one ormore XR services. For example, based on the uplink information, thecloud XR entity may identify landmarks, opportunities for userinteraction, and/or opportunities for performing a transaction. In suchexamples, the cloud XR entity may generate the rendering information toinclude XR information associated with the respective services.

In some examples, the cloud XR entity may provide granular control of XRservices supported by the vehicle XR session. For example, a vehicle XRsession may be subscription-based and associated with a subscriptionlevel. A subscription level may be associated with a quantity of userstreams that may be associated with a vehicle XR session. For example, afirst subscription level may permit only driver stream, a secondsubscription level may permit only a passenger stream, a thirdsubscription level may permit a driver stream and a passenger stream,and a fourth subscription level may permit any number and combination ofstreams. In some examples, a subscription level may be associated with alevel of XR interactivity. For example, based on the subscription level,the cloud XR entity may generate XR information including differenttypes of interactive objects. In some examples, the subscription levelmay be associated with which services are enabled and/or disabled. Forexample, one subscription level may include navigation services andlandmark services, while another subscription level may includenavigation services, landmark services, interactivity services, andtransaction-enabling enabling services, etc. Thus, according to one ormore examples, different subscription levels may result in different XRinformation being presented to users. In some examples, the subscriptionlevel may additionally, or alternatively, determine what kind ofservices can be presented to the user. For example, at some subscriptionlevels, a high priority service user, e.g., a police officer, agovernment official, etc., may be presented with landmark services orinteractive services from all surrounding buildings/locations, whileusers who are not high priority service users (e.g., “normal” users),may be presented with only services from commercial buildings/locations.

When establishing the vehicle XR session with the vehicle UE, the cloudXR entity may authorize a supported session level based on thesubscription level. The supported session level may indicate which XRservices are enabled and/or disabled and provide XR informationaccordingly. In some examples, the supported session level may be basedon QoS information and/or QoE information. For example, the cloud XRentity may perform rendering adaptation to provide a satisfactory userexperience. The rendering adaptation may be based on QoE metrics and/orQoS support information provided by the vehicle UE. For example, whencommunications between the vehicle UE and the cloud XR entity aredelayed, packet retransmission is being observed, and/or the data rateis lower than allowed, the cloud XR entity may perform renderingadaptation to adjust the XR information being generated and provided tothe vehicle UE. For example, when the QoE metrics and/or the QoS supportinformation indicates reduced communication capabilities, the cloud XRentity may prioritize XR information associated with a driver stream andmay deprioritize XR information associated with passenger streams. Inthis manner, the cloud XR entity may provide a satisfactory userexperience to the driver, which may be of higher priority than providinga satisfactory user experience to the passengers, for example.

In some examples, the vehicle XR session may be associated with multipleusers. For example, the vehicle XR session may include a first userstream associated with a first user (e.g., a driver) and a second userstream associated with a second user (e.g., a passenger). In suchexamples, the user streams may be associated with the same vehicle(e.g., the vehicle 500 of FIG. 5 ). For example, the uplink informationmay include a first user XR component associated with the first user, asecond user XR component associated with the second user, and a vehicleXR component that is shared between the first stream and the secondstream. The cloud XR entity may receive the uplink information and therespective components and consolidate the uplink information so that therendering information facilitates a unified projection to the one ormore displays of the vehicle.

Referring again to the example vehicle 500 of FIG. 5 , the vehicle XRsystem of the vehicle 500 may be associated with one or more displays.The displays may be glasses-based or glass-less. In a glasses-baseddisplay, the users may each be wearing individual XR glasses and XRinformation may be displayed separately on the different XR glasses. Ina glass-less based display, XR information may be presented via aheads-up display (HUD). In some examples, to enable different XRinformation to be presented for different users, the HUD may be aspecial-treated window that is polarized to achieve dual view ofdifferent content.

In the example of FIG. 5 , the vehicle 500 includes the first display510 that may be a HUD and configured to display XR information for thedriver 502 and the first passenger 504. The vehicle 500 also includes asecond display 520 that is positioned on the driver-side of the vehicle500 and a third display 522 that is positioned on the other side of thevehicle 500. The second display 520 and the third display 522 may beHUDs configured to display XR information to users on therespective-sides of the vehicle. In some examples, the third display 522may be configured to display different XR information to the firstpassenger 504 and the second passenger 506. The vehicle 500 alsoincludes a fourth display 530. The fourth display 530 may be aglasses-based display that is worn by the second passenger 506 to viewXR information associated with a vehicle XR session. Thus, it may beappreciated that when the vehicle UE 514 of FIG. 5 receives renderinginformation (e.g., from the cloud XR entity), the rendering informationmay be presentment via the one or more displays of the vehicle 500(e.g., the first display 510, the second display 520, the third display522, and/or the fourth display 530).

It may be appreciated that in other examples, the positioning of thedisplays and/or types of the displays may vary. For example, a vehiclemay include only glasses-based displayed or may include only glass-lessbased displayed.

As used herein, the term “XR information” refers to information thatrendered in association with an XR session. For example, XR informationmay include augmentation information that is superimposed over realworld objects, such as the augmentation information 620 of FIG. 6Aand/or the augmentation information of FIG. 6C.

FIG. 7 illustrates an example communication flow 700 between a networkentity 702, a vehicle UE 704, and a cloud XR entity 708, as presentedherein. One or more aspects described for the network entity 702 may beperformed by a component of a base station or a component of a basestation, such as a CU, a DU, and/or an RU. Aspects of the cloud XRentity 708 may facilitate implementing the vehicle-to-cloud XR component191 and/or the vehicle-to-cloud XR network component 199 of FIG. 1 .Although not shown in the illustrated example of FIG. 7 , it may beappreciated that in additional or alternate examples, the network entity702, the vehicle UE 704, and/or the cloud XR entity 708 may be incommunication with one or more other network entities or UEs.

In the illustrated example of FIG. 7 , the communication flow 700facilitates establishing a vehicle XR session and management of thevehicle XR session between the vehicle UE 704 and the cloud XR entity708. The vehicle UE 704 may be a UE that enables a vehicle 706 tocommunicate via an access network. The vehicle 706 may be a terrestrialvehicle, such as a car, a bus, a train, etc., or may be anairborne/non-terrestrial vehicle, such as a drone, a balloon, etc. Thecloud XR entity 708 may be a network entity that providesvehicle-to-cloud-based XR services to the vehicle 706. In some examples,the cloud XR entity 708 may be operated by a network operator, such asan operator of the network entity 702. In other examples, the cloud XRentity 708 may be operated by an operator different than the operator ofthe network entity 702. The network entity 702 and the cloud XR entity708 may be collocated in a physical entity in some realizations.

As shown in FIG. 7 , the vehicle UE 704 and the cloud XR entity 708perform respective connection establishment procedures to facilitatecommunication between the vehicle UE 704 and the cloud XR entity 708.For example, the vehicle UE 704 and the network entity 702 perform afirst connection establishment procedure 710 to enable the vehicle UE704 to communicate via an access network. The cloud XR entity 708 andthe network entity 702 may also perform a second connectionestablishment procedure 712 to enable the cloud XR entity 708 tocommunicate via the access network.

In the example of FIG. 7 , after the vehicle UE 704 and the cloud XRentity 708 establish their respective connections, the vehicle UE 704and the cloud XR entity 708 may communicate via the network entity 702.For example, when the vehicle UE 704 transmits a message to the cloud XRentity 708, the message may be first communicated from the vehicle UE704 to the network entity 702, and then from the network entity 702 tothe cloud XR entity 708. In a similar manner, when the cloud XR entity708 transmits a message to the vehicle UE 704, the message may be firstcommunicated from the cloud XR entity 708 to the network entity 702, andthen from the network entity 702 to the vehicle UE 704.

As shown in FIG. 7 , the vehicle UE 704 and the cloud XR entity 708 mayperform a session establishment procedure 720 to establish a vehicle XRsession. The session establishment procedure 720 may enable the vehicleUE 704 to initiate a vehicle XR session with the cloud XR entity 708.The session establishment procedure 720 may also enable the cloud XRentity 708 to authorize a vehicle XR session and to configure one ormore aspects of the vehicle XR session

For example, the vehicle UE 704 may output (e.g., transmit) a sessionrequest 722 that is obtained (e.g., received) by the cloud XR entity708. The session request 722 may include a request to establish avehicle XR session. The cloud XR entity 708 may perform authorizationprocedures 724 to authorize a vehicle XR session 726. The cloud XRentity 708 may perform the authorization procedures 724 based oninformation included in the session request 722. The cloud XR entity 708may then output a session response 728 that is received by the vehicleUE 704. The session response 728 may confirm that the vehicle XR session726 is established between the vehicle UE 704 and the cloud XR entity708.

The vehicle XR session 726 may be associated with a session level and acorresponding session configuration. The session level may be based onone or more of a subscription, a supported Quality of Service (QoS), auser identifier (ID), and/or privacy controls. In some examples, thecloud XR entity 708 may determine a session configuration based on thesession level. The session configuration may be associated with one ormore operation parameters. For example, the session configuration mayindicate a Uu connection to establish, an update frequency of stateinformation, etc. The cloud XR entity 708 may configure the vehicle UE704 with the one or more operation parameters via the session response728. Additional aspects of the session establishment procedure 720 aredescribed in connection with FIG. 8 .

After the vehicle XR session 726 is established (e.g., via the sessionestablishment procedure 720), the vehicle UE 704 and the cloud XR entity708 may perform session management procedures 730 to manage the userexperience associated with the vehicle XR session 726. For example, thevehicle UE 704 may perform collection procedures 732 to collectinformation at the vehicle 706. For example, one or more sensors of thevehicle 706 may be configured to collect information related to the userand/or to the vehicle 706. Aspects of the one or more sensors of thevehicle 706 may be implemented by the one or more sensors 512 of FIG. 5. For example, the one or more sensors of the vehicle 706 may includesensors associated with an ADAS system of the vehicle 706 and/orin-cabin sensors.

As shown in FIG. 7 , the vehicle UE 704 may output uplink information734 that is obtained by the cloud XR entity 708. The uplink information734 may be based on the information collected via the collectionprocedures 732. In the example of FIG. 7 , the uplink information 734includes a vehicle XR component 736 and a user XR component 738. Thevehicle XR component 736 may include information relating to the vehicle706, such as vehicle posture information, vehicle information, and/orvehicle-surrounding information. The user XR component 738 may includeinformation relating to the user, such as user pose information and/oruser input information.

In some examples, the vehicle UE 704 may collect information associatedwith the vehicle XR component 736 and/or the user XR component 738 basedon respective periodicities configured via the session response 728. Asdifferent sensors may be associated with the collection of informationfor the vehicles and the users, the information collection may happen atdifferent time points and/or with different periodicities. In someexamples, the vehicle UE 704 may include timing information (e.g.,timestamps) associated with different attributes of the uplinkinformation.

As shown in FIG. 7 , the cloud XR entity 708 may perform combinationprocedures 740 based on the uplink information 734. For example, thecloud XR entity 708 may perform virtual-physical fusion based on thevehicle XR component 736 and the user XR component 738 of the uplinkinformation 734. In some examples, the combination procedures 740 mayinclude associating an augmentation component with vehicle-surroundinginformation based on an environmental component. For example, the cloudXR entity 708 may identify an environmental component (e.g., a realworld object) based on the vehicle XR component 736 of the uplinkinformation 734. The cloud XR entity 708 may then associate anaugmentation component with the environmental component. For example,the cloud XR entity 708 may identify a stadium and associated anaugmentation component with the stadium. The augmentation component mayinclude one or more of an identifier of a landmark (e.g., a name of thestadium) and an interactive object. The interactive object may beselected by the user to access additional information related to thereal world object.

In some examples, the combination procedures 740 may include combininginformation from the vehicle UE 704 (e.g., the uplink information 734)and information from a service entity providing a service. Aspects ofcombining information based on information from a service entity aredescribed in connection with the examples of FIG. 14 and FIG. 15 .

In some examples, the combination procedures 740 may include correlatingmultiple attributes of the uplink information based on at least a firsttimestamp and a second timestamp. For example, the vehicle XR component736 may include at least a first timestamp and the user XR component 738may include at least a second timestamp. The cloud XR entity 708 may usethe first timestamp and the second timestamp to correlate attributes ofthe uplink information 734 and/or compensate for differences indifferent attributes of the uplink information 734.

The cloud XR entity 708 may perform determination procedures 742 todetermine what information to provide to the vehicle UE 704. Forexample, the cloud XR entity 708 may determine different XR informationto provide to the vehicle UE 704 based on, for example, a subscriptionlevel, a QoS profile, a user identifier, privacy controls, etc. Forexample, based on a subscription level and corresponding supportedsession level associated with the vehicle XR session 726, the cloud XRentity 708 may determine to include different levels of interactivityvia the XR information provided to the vehicle UE 704.

The cloud XR entity 708 may perform generating procedures 744 togenerate rendering information 746. The rendering information 746 may bebased on the output of the combination procedures 740 and thedetermination procedures 742. In some examples, the renderinginformation 746 may be configured based on the display capabilities ofthe vehicle 706. For example, the cloud XR entity 708 may adjust therendering information 746 based on whether the rendering information 746is for presentment via a glasses-based display or a glass-less baseddisplay. The cloud XR entity 708 may then output the renderinginformation 746 that is obtained by the vehicle UE 704.

As shown in FIG. 7 , the vehicle UE 704 may perform presentationprocedures 748 to present the rendering information 746. For example,the vehicle UE 704 may present the rendering information 746 via the oneor more displays of the vehicle 706. Aspects of the displays of thevehicle 706 may be implemented by the first display 510, the seconddisplay 520, the third display 522, and/or the fourth display 530 ofFIG. 5 .

FIG. 8 illustrates an example communication flow 800 between a networkentity 802 and a vehicle UE 804, as presented herein. Aspects of thenetwork entity 802 may be implemented by the cloud XR entity 708. In theillustrated example of FIG. 8 , the communication flow 800 facilitatesestablishing a vehicle XR session between the network entity 802 and thevehicle UE 804. For example, the communication flow 800 may facilitateperforming the session establishment procedure 720 of FIG. 7 . Inanother example, the signaling between the vehicle UE 804 and thenetwork entity 802 may be forwarded by the network entity 702 of FIG. 7.

As shown in FIG. 8 , the vehicle UE 804 may transmit a session request810 that is obtained (e.g., received) by the network entity 802. Asdescribed in connection with the session request 722 of FIG. 7 , thesession request 810 may indicate a request to establish a vehicle XRsession with the network entity 802. The session request 810 may alsoindicate information that the network entity 802 may use to establishand maintain the vehicle XR session. In some examples, the sessionrequest 810 may include vehicle information 812, QoS information 814,subscription credential information 816, and/or subscription requestinformation 818. Although the vehicle information 812, the QoSinformation 814, the subscription credential information 816, and thesubscription request information 818 are illustrated as separatecommunications in the example of FIG. 8 , in other examples, one or moreof the vehicle information 812, the QoS information 814, thesubscription credential information 816, and/or the subscription requestinformation 818 may be included with the session request 810.

In some examples, the vehicle UE 804 may transmit the vehicleinformation 812 that is obtained by the network entity 802. The vehicleinformation 812 may include information about a vehicle associated withthe vehicle UE 804, such as the vehicle 706 of FIG. 7 . The vehicleinformation 812 may include vehicle make information, vehicle modelinformation, vehicle modem information, vehicle mobile equipment (ME)information, path plan information, traffic condition information, etc.In some examples, the path plan information may be provided via anavigation system of the vehicle. For example, the path plan informationmay indicate a destination and a route to arrive at the destination. Insome examples, the traffic condition information may be associated withtraffic light information obtained from other devices, for example, viasidelink communication. Some examples of sidelink communication mayinclude vehicle-based communication devices that can communicate fromvehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., fromthe vehicle-based communication device to road infrastructure nodes suchas a Road Side Unit (RSU)), vehicle-to-network (V2N) (e.g., from thevehicle-based communication device to one or more network nodes, such asa base station), vehicle-to-pedestrian (V2P), cellularvehicle-to-everything (C-V2X), and/or a combination thereof and/or withother devices, which can be collectively referred to asvehicle-to-anything (V2X) communications. In some examples, the networkentity 802 may obtain the vehicle information via a third partydifferent than the vehicle UE 804. For example, the network entity 802may obtain the vehicle information directly from the RSU, from anotherUE, or using other connected sensors, including cameras or radars.

In some examples, the vehicle UE 804 may transmit the QoS information814 that is obtained by the network entity 802. The QoS information 814may indicate a data rate supported by the vehicle UE 804 and/or mobiledevices of users associated with the vehicle XR session. The QoSinformation 814 may also, or alternatively, indicate if a networkconnection is already established by the vehicle UE 804 (e.g., via thefirst connection establishment procedure 710 of FIG. 7 ). In some suchexamples, the QoS information 814 may also indicate if associatedprotocol data unit (PDU) sessions are established and if there are anyguaranteed bit rate (GBR) bearers established. In some examples, the QoSinformation 814 may include an identifier of the UE, such as a genericpublic subscription identifier (GPSI). The identifier of the UE mayenable the network entity 802 to obtain QoS monitoring/predictioninformation from another network entity, such as the AMF 192 of FIG. 1 .

In some examples, the vehicle XR session may be associated with asubscription. A subscription may facilitate receiving one or moreservices associated with a vehicle XR session. A subscription mayprovide the one or more services to only one user (e.g., a driver or apassenger) or to more than one user (e.g., a driver and one or morepassengers, or two or more passengers) associated with the vehicle XRsession. In some examples, the subscription may be associated withdifferent sets of services to different users. For example, thesubscription may provide a first set of services (e.g., one or moreservices) to a driver and may provide a second set of services (e.g.,one or more services) to a passenger. In some examples, the subscriptionmay be associated with different sets of services for passengers. Forexample, the set of services offered to a passenger may be based on anage of the passenger (e.g., different sets of services associated withchildren, teenagers, adults, etc.) and/or a position of the passenger inthe vehicle (e.g., different sets of services associated with apassenger in the front row compared to a passenger in a back row).

In some examples, the subscription may be a vehicle-based subscription.A vehicle-based subscription may be associated with a vehicle (e.g., thevehicle 706 of FIG. 7 ) and the one or more services may be registeredwith the vehicle. For example, a vehicle-based subscription may providethe one or more services to users of the vehicle.

In some examples, the subscription may be a user-based subscription. Auser-based subscription may be associated with a user (e.g., via a useridentifier) and the one or more services may be registered with theuser. For example, a user-based subscription may enable a user to accessthe one or more services associated with their subscription fromdifferent vehicles, such as a rental vehicle. In some examples, theuser-based subscription may allow a user to transfer a vehicle XRsession from one vehicle to another vehicle, for example, in a ridesharing case. The user-based subscription information may be locallyshared with the vehicle UE 804 so that it can be used for thecorresponding vehicle XR session control. The local sharing mechanismfor the subscription information may depend on the connectivityavailable in the vehicle, e.g., via Bluetooth, Wi-Fi, or otherdevice-to-device communication technologies.

The subscription may be an existing subscription or may be requested. Insome examples, the vehicle UE 804 may transmit the subscriptioncredential information 816 that is obtained by the network entity 802.The subscription credential information 816 may include credentialsassociated with an existing subscription for vehicle XR services. Thecredentials may be stored in and/or associated with a subscriberidentity module (SIM), a vehicle mobile equipment (ME), and/or an IPmultimedia subsystem (IMS) like credentials. For example, an MEidentifier, e.g., an International Mobile Equipment Identity (IMEI) or aUE ID, may be used for authorization and/or authentication. In someexamples, the credential may be stored in a virtual SIM, a secureenvironment of a ME, or a physical security token. In some examples, thecredential may additionally or alternatively use different formats thatcan be supported by the network entity 802, such as 3GPP definedcredentials, or other credentials including certificates issued orauthorized by other authorities, etc.

In some examples, the vehicle UE 804 may transmit the subscriptionrequest information 818 that is obtained by the network entity 802. Thesubscription request information 818 may include information associatedwith creating a subscription for vehicle XR services. Aspects of thesubscription request information 818 may be collected via an onlinesign-up procedure, an application store, and/or payment information(e.g., a credit card, mobile payment, etc.).

As shown in FIG. 8 , the network entity 802 may perform authorizationprocedures 820 to establish a vehicle XR session 826. In some examples,the authorization procedures 820 may include subscription managementprocedures 822. For example, the network entity 802 may performsubscription sign-up and subscription control. For example, the networkentity 802 may create a subscription based on the subscription requestinformation 818. In some examples, the network entity 802 may verify thesubscription credential information 816 to confirm that the vehicle UE804 is authorized to access a vehicle XR session.

The network entity 802 may also determine a supported session level 824.The network entity 802 may determine the supported session level 824based on information obtained and/or associated with the session request810, such as the vehicle information 812, the QoS information 814,and/or the subscription credential information 816. For example, thesupported session level 824 may be associated with a subscription level,a supported QoS, a user identifier, and/or privacy controls. Thesupported session level 824 may enable the network entity 802 to performgranular support of services supported by the vehicle XR session 826.For example, based on a supported session level 824, the network entity802 may determine to enable and/or disable one or more services and/ormay determine a level of XR interactivity.

In some examples, the supported session level 824 may be based in parton a location and/or path plan of the vehicle. For example, the vehicleinformation 812 may indicate the location of the vehicle and/or a pathplan of the vehicle. The network entity 802 may obtain, based on thevehicle information 812, supported QoS along the path plan of thevehicle (e.g., via predicted QoS procedures) and determine the supportedsession level 824 for the vehicle XR session 826 based on the supportedQoS. For example, the network entity 802 may determine, based on thevehicle information 812, that portions of the path plan may have varyinglevels of network support capabilities and, thus, adjust the supportedsession level 824 for the vehicle XR session 826.

Determining the supported session level 824 based on the supported QoSmay enable the network entity 802 to ensure that the user experience ofa user (e.g., a driver) is not diminished. The supported session level824 may be used in-turn by the network entity 802 to scheduletransmission planning, encoding of the information, or even feedback tothe network entity 702 of FIG. 7 to adjust the rendering informationconstructions. For example, in examples in which the vehicle XR session826 is associated with multiple users (e.g., a driver and one or morepassengers), the network entity 802 may determine the supported sessionlevel 824 so that that passenger XR session(s) do not interfere with thedriver experience. For example, different session levels may offerdifferent levels of XR interactivity and the supported session level 824may be associated with a level of XR interactivity based on thesupported QoS.

In some examples, the network entity 802 may determine the supportedsession level 824 based on the location of the vehicle UE 804. Forexample, the vehicle information 812 may include vehicle-surroundinginformation indicating that the vehicle is traveling next to a barricadeon one-side of the vehicle. In such examples, the supported sessionlevel 824 may adjust the information provided to the vehicle UE 804 sothat information for presentment on the barricaded-side is reduced,thereby reducing the amount of information communicated to the vehicleUE 804.

In some examples, the network entity 802 may determine the supportedsession level 824 based on a user and/or privacy controls. For example,different services may be associated with different users. In suchexamples, the XR information presented to a user may be based on theirassociated services. For example, certain public locations/services mayoffer XR information. In such examples, certain users may be presentedwith the XR information while other users may not be presented with theXR information. For example, a user who is a police officer may bepresented with XR information that is not presented to a user who is nota police officer. As another example, a real estate agent may bepresented with house-based XR information associated with a house whilethe general public may not be presented with the house-based XRinformation and/or may be presented with limited house-based XRinformation. For example, the real estate agent may see informationindicating that the house is on the market, while the general public maysee no information about the house or may see a house address.

As another example, if a user has a subscription to a sports channel,then the user may be presented with additional XR information and/ormore in-depth information compared to a user who does not have thesubscription to the sports channel. For example, one supported sessionlevel may provide information, such as a stadium name, when a stadium isvisible and another supported session level may provide additionalinformation related to the stadium, such as the home team(s) of thestadium, whether there is a game being played (or was recently played),the score of the game, a schedule of games, etc.

Thus, the supported session level 824 may facilitate the network entity802 determining what information to provide to the vehicle UE 804 forpresentment associated with the vehicle XR session 826. For example,based on the supported session level 824 and in association with thevehicle XR session 826, the network entity 802 may determine what XRinformation to provide to the vehicle UE 804 and/or may determine howmuch XR information to provide to the vehicle UE 804.

As shown in FIG. 8 , the network entity 802 may output a sessionresponse 830 that is obtained (e.g., received) by the vehicle UE 804. Asdescribed in connection with the session response 728 of FIG. 7 , thesession response 830 may confirm that the vehicle XR session 826 isestablished between the vehicle UE 804 and the network entity 802.

In some examples, the session response 830 may include a sessionconfiguration 832. The session configuration 832 may configure one ormore operating parameters associated with the vehicle XR session 826 atthe vehicle UE 804. For example, the session configuration 832 mayinclude an indication of the supported session level 824 associated withthe vehicle XR session 826. The session configuration 832 may be basedon the supported session level 824. In some examples, the sessionconfiguration 832 may configure a network connection type at the vehicleUE 804. In some examples, the session configuration 832 may configure anupdate frequency (e.g., periodicity) associated with uplink informationassociated with the vehicle XR session 826. For example, the sessionconfiguration 832 may configure a first periodicity associated with avehicle XR component of uplink information (e.g., the vehicle XRcomponent 736 of FIG. 7 ) and may configure a second periodicityassociated with a user XR component of the uplink information (e.g., theuser XR component 738 of FIG. 7 ).

In some examples, the network entity 802 may provide a configurationassociated with Quality of Experience (QoE) parameters for the vehicleXR session 826. For example, the network entity 802 may output a QoEmeasurement configuration 834 that is received by the vehicle UE 804.The QoE measurement configuration 834 may be based on the supportedsession level 824 and/or the QoS information 814. The QoE measurementconfiguration 834 may facilitate providing fast and accurate renderinginformation to the vehicle UE 804. For example, the QoE measurementconfiguration 834 may facilitate accurate placement of augmentationcomponents for presentment at the vehicle. In some examples, the QoEmeasurement configuration 834 may be associated with a delay and/or acapacity. For example, the QoE measurement configuration 834 mayconfigure a delay threshold, a retransmission threshold, and/or a datarate threshold.

In some examples, the vehicle UE 804 may collect QoE metrics based onthe QoE measurement configuration 834. Examples of QoE metrics mayinclude a delay associated with a transmission, observed packetretransmission, and/or a data rate. In some examples, the vehicle UE 804may transmit the session request 810 when an event associated with QoEmetrics is satisfied. For example, the vehicle UE 804 may transmit thesession request 810 when the delay exceeds the delay threshold, observedpacket retransmission exceeds the retransmission threshold, and/or thecapacity does not satisfy the data rate threshold (e.g., the data rateis lower than allowed by the network).

Although the session configuration 832 and the QoE measurementconfiguration 834 are illustrated as separate communications in theexample of FIG. 8 , in other examples, one or both of the sessionconfiguration 832 and the QoE measurement configuration 834 may beincluded with the session response 830.

FIG. 9 illustrates an example communication flow 900 between a networkentity 902 and a vehicle UE 904, as presented herein. Aspects of thenetwork entity 902 may be implemented by the cloud XR entity 708 of FIG.7 and/or the network entity 802 of FIG. 8 . Aspects of the vehicle UE904 may be implemented by the vehicle UE 704 of FIG. 7 and/or thevehicle UE 804 of FIG. 8 .

In the illustrated example of FIG. 9 , the communication flow 900facilitates providing vehicle-to-cloud XR services associated with avehicle XR session. For example, the vehicle UE 904 and the networkentity 902 may establish a vehicle XR session 910, as described inconnection with session establishment procedure 720 of FIG. 7 and/or thecommunication flow 800 of FIG. 8 . The vehicle XR session 910 mayinclude one or more information streams that facilitate exchanginginformation associated with a respective user between the network entity902 and the vehicle UE 904. As shown in FIG. 9 , the vehicle XR session910 includes a first user XR stream 930 and a second user XR stream 950.The first user XR stream 930 may facilitate exchanging informationassociated with a first user, such as the driver 502 of FIG. 5 . Thesecond user XR stream 950 may facilitate exchanging informationassociated with a second user, such as the first passenger 504 of FIG. 5. Although the example of FIG. 9 includes two information streams (e.g.,the first user XR stream 930 and the second user XR stream 950), whichmay also be referred to as “sub-sessions” or “layers” of the vehicle XRsession, other examples may include any suitable quantity of informationstreams, for example, based on a quantity of users accessing the vehicleXR session 910.

The vehicle UE 904 may transmit uplink information that is obtained bythe network entity 902, as described in connection with the uplinkinformation 734 of FIG. 7 . The uplink information may include one ormore components. In the example of FIG. 9 , the vehicle UE 904 transmitsa vehicle XR component 920 that is obtained by the network entity 902.The vehicle XR component 920 may include vehicle posture information 922(e.g., location information, orientation information, directioninformation, heading information, speed information, yaw information,etc.), vehicle information 924 (e.g., vehicle make information, vehiclemodel information, vehicle modem information, vehicle mobile equipment(ME) information, path plan information, navigation information, trafficcondition information, etc.), and/or vehicle-surrounding information 926(e.g., environment information, buildings information, landscapeinformation, etc.).

As shown in FIG. 9 , the vehicle XR session 910 includes a first user XRstream 930 that may facilitate communicating information between thenetwork entity 902 and the vehicle UE 904 associated with a first user(e.g., the driver 502 of FIG. 5 ). For example, the first user XR stream930 may include a component of uplink information, such as a first userXR component 932. The first user XR component 932 may include user poseinformation 934 (e.g., a position and/or orientation of the first user).The user pose information 934 may be relative pose information and/orabsolute pose information. For example, the user pose information 934that is with respect to the ground may be referred to as absolute userpose information. The user pose information 934 that is with respect avehicle coordinate system may be referred to as relative user poseinformation. The first user XR component 932 may also, or alternatively,include user input information 936. The user input information 936 mayinclude information related to eye tracking, such as length of eyefocus, and/or user gesture information associated with the first user.The user input information 936 may facilitate identifying when the firstuser is providing user input, such as selecting an augmentationcomponent (e.g., an interactive object) being presented via therendering information.

The first user XR stream 930 also includes first user renderinginformation 940. For example, the network entity 902 may output thefirst user rendering information 940 that is received by the vehicle UE904. The first user rendering information 940 may include renderinginformation configured for presentment via the one or more displaysassociated with the first user. For example, and referring to theexample of FIG. 5 , the first user rendering information 940 may bepresented to the driver 502 via the first display 510 when the driver islooking forward and may be presented to the driver 502 via the seconddisplay 520 when the driver 502 is looking in the direction of thewindow 516.

The first user rendering information 940 may include XR informationconfigured for providing a satisfactory user experience to the firstuser. For example, the first user rendering information 940 may includeaugmentation components associated with a path plan (e.g., directions),a landmark, and/or interactive objects. The augmentation components maybe associated with vehicle-surrounding information. For example, thenetwork entity 902 may identify an environmental component via thevehicle XR component 920 (e.g., a landmark, such as a stadium). Thenetwork entity 902 may then associate an augmentation component with thevehicle-surrounding information based on the environmental component.For example, the network entity 902 may associate an identifier of alandmark (e.g., a stadium name) with the environment component. Thus,the first user rendering information 940 may include augmentationcomponents associated with real world objects and related to the userexperience of the first user.

As shown in FIG. 9 , the vehicle XR session 910 may also include asecond user XR stream 950 that may facilitate communicating informationbetween the network entity 902 and the vehicle UE 904 associated with asecond user (e.g., the first passenger 504 or the second passenger 506of FIG. 5 ). For example, the second user XR stream 950 may include acomponent of uplink information, such as a second user XR component 952.The second user XR component 952 may be similar to the first user XRcomponent 932, but with respect to the second user. For example, thesecond user XR component 952 may include user pose information 954(e.g., a position and/or orientation of the second user). The user poseinformation 954 may be relative pose information and/or absolute poseinformation. The second user XR component 952 may also, oralternatively, include user input information 956. The user inputinformation 956 may include information related to eye tracking, such aslength of eye focus, and/or user gesture information associated with thesecond user. The user input information 956 may facilitate identifyingwhen the second user is providing user input, such as selecting anaugmentation component (e.g., an interactive object) being presented viathe rendering information.

The second user XR stream 950 also includes second user renderinginformation 960. For example, the network entity 902 may output thesecond user rendering information 960 that is received by the vehicle UE904. Similar to the first user rendering information 940 associated withthe first user XR stream 930, the second user rendering information 960may include rendering information configured for presentment via the oneor more displays associated with the second user. For example, andreferring to the example of FIG. 5 , the second user renderinginformation 960 may be presented to the first passenger 504 via thefirst display 510 when the first passenger 504 is looking forward andmay be presented to the first passenger 504 via the third display 522when the first passenger is looking in the direction of the thirddisplay 522.

Similar to the first user rendering information 940, the second userrendering information 940 may include XR information configured forproviding a satisfactory user experience to the second user. Forexample, the second user rendering information 960 may includeaugmentation components associated with real world objects. Theaugmentation components may include identifiers of the real worldobjects and/or interactive objects.

In the example of FIG. 9 , the rendering information may be based on theuser XR component and the vehicle XR component. Thus, in some examples,the vehicle XR component 920 may be shared between the first user XRstream 930 and the second user XR stream 950. The communicationsassociated with the different user sessions may be communicatedseparately or may be communicated together. For example, the vehicle UE904 may transmit uplink information including the vehicle XR component920, the first user XR component 932, and/or the second user XRcomponent 952. Additionally, the network entity 902 may output renderinginformation including the first user rendering information 940 and/orthe second user rendering information 960. For example, the renderinginformation may include a first rendering information componentcorresponding to the first user rendering information 940 and a secondrendering information component corresponding to the second userrendering information 960.

As shown in FIG. 9 , one or more aspects of the uplink information(e.g., the vehicle XR component 920, the first user XR component 932,and/or the second user XR component 952) may include timing information.For example, the vehicle XR component 920 may be associated with a firsttimestamp 928, the first user XR component 932 may be associated with asecond timestamp 938, and the second user XR component 952 may beassociated with a third timestamp 958. The respective timestamps mayinclude a date and/or time at which the corresponding information wascollected. The timing information may facilitate correlating attributesof the uplink information and/or compensating for attributes of theuplink information. Aspects of correlating and/or compensating theattributes of the uplink information are described in connection withthe communication flow 1400 of FIG. 14 .

FIG. 10 is a diagram illustrating information 1000 that may be exchangedwith a network entity, as presented herein. The information 1000 may becollected by a UE for communicating to a network entity. Aspects ofcollecting the information 1000 are described in connection with thecollection procedures 732 of FIG. 7 . For example, the information maybe collected via one or more sensors of a vehicle, such as the one ormore sensors 512 of the vehicle 500 of FIG. 5 .

In the example of FIG. 10 , the information 1000 includes aspects of avehicle XR component 1010, such as vehicle posture information. Thevehicle XR component 1010 may include information related to theposition and/or orientation of a vehicle 1002. For example, the vehicleXR component 1010 of FIG. 10 may include a vehicle orientation,velocity, heading, yaw, pitch, and/or roll. The vehicle XR component1010 may be based on a relative positioning or absolute positioning.Examples of absolute positioning are shown in FIG. 10 via labels X_(E),Y_(E), and Z_(E). Examples of relative positioning are shown in FIG. 10via labels X_(V), Y_(V), and Z_(V). The vehicle XR component 1010 mayalso include surrounding environments of the vehicle 1002, such as thevehicle-surrounding information 926 of FIG. 9 . The vehicle XR component1010 may also, or alternatively, include a path plan (e.g., from anavigation system) that provides directions to a desired destination.

In the example of FIG. 10 , the information 1000 may also includeaspects of a user XR component 1020, such as user pose information. Theuser pose information may refer to a position and/or orientation of theuser in space relative to an XR space. For example, the user XRcomponent 1020 may include an orientation of the user. The user XRcomponent 1020 may also include video and/or camera inputs, such assurrounding environments, user eye tracking, and/or user gestures (e.g.,based on hand devices).

In some examples, the information 1000 associated with the user XRcomponent 1020 may correspond to an absolute posture, for example, withrespect to the ground. In some examples, the user XR component 1020 maycorrespond to a relative posture, for example, with respect the vehiclecoordinate system. For example, the orientation of the user may be withrespect to the ground (e.g., an absolute posture) or may be with respectto the vehicle coordinate system (e.g., a relative posture). In asimilar manner, the user gestures may be described with respect to theground (e.g., an absolute gesture) or may be with respect to the vehiclecoordinate system (e.g., a relative gesture). In some examples,information related to the relative gestures and/or the relative posturemay be collected via in-cabin sensors of the vehicle 1002.

FIG. 11 illustrates a communication flow 1100 between a network entity1102 and a vehicle UE 1104, as presented herein. Aspects of the networkentity 1102 may be implemented by a vehicle-to-cloud platform, such asthe cloud XR entity 708 of FIG. 7 and/or the network entity 802 of FIG.8 . Aspects of the vehicle UE 1104 may be implemented by an XR-enabledvehicle, such as the vehicle 500 of FIG. 5 and/or the vehicle UE 704 andvehicle 706 of FIG. 7 .

In the illustrated example of FIG. 11 , the network entity 1102 and thevehicle UE 1104 communicate via a communication system 1106. Aspects ofthe communication system 1106 are described in connection with thenetwork entity 702 of FIG. 7 . For example, the network entity 1102 andthe vehicle UE 1104 may communicate via a 5G NR system.

As shown in FIG. 11 , the vehicle UE 1104 may transmit an XR sessionrequest 1110 that is obtained (e.g., received) by the network entity1102. Aspects of the XR session request 1110 may be implemented by thesession request 722 of FIG. 7 and/or the session request 810 of FIG. 8 .In the illustrated example of FIG. 11 , the vehicle UE 1104 may transmitQoS support information 1112 associated with the XR session request1110. The QoS support information 1112 may facilitate XR renderingadaptation by the network entity 1102.

The QoS support information 1112 may include a data rate supported bythe vehicle and/or mobile devices of users associated with the vehicleXR session. In some examples, the QoS support information 1112 mayindicate if a network connection is already established (e.g., via thecommunication system 1106). For example, the QoS support information1112 may indicate that the vehicle UE 1104 has established a networkconnection with the communication system 1106 and whether there are oneor more XR-based PDU sessions associated with the network connection.For example, an XR-based PDU session may be associated with a QoS Flowthat requires a guaranteed flow bit rate (e.g., GBR QoS Flow) and, thus,the QoS support information 1112 may indicate whether one or more GBRbearers are established to facilitate the communication associated withthe vehicle XR session.

In some examples, the XR session request 1110 may include a vehicleidentifier 1114. For example, the vehicle identifier 1114 may include avehicle ME identifier, a UE ID, a GPSI, etc. The network entity 1102 mayuse the vehicle identifier 1114 to obtain QoS monitoring informationand/or QoS prediction information from the communication system 1106.For example, the network entity 1102 may output a request 1120 that isobtained by the communication system 1106. The request 1120 may includethe vehicle identifier 1114. The communication system 1106 may use thevehicle identifier 1114 to obtain QoS monitoring information and/or QoSprediction information associated with the vehicle UE 1104. Thecommunication system 1106 may then transmit a response 1122 based on therequest 1120 and include the QoS monitoring information and/or QoSprediction information.

In some examples, the network entity 1102 may configure the vehicle UE1104 to collect and provide QoE metrics. For example, to facilitate XRrendering adaptation, the network entity 1102 may output a QoEmeasurement configuration 1130 that is received by the vehicle UE 1104.In some examples, the network entity 1102 may provide the QoEmeasurement configuration 1130 via a session response, such as thesession response 728 of FIG. 7 and/or the session response 830. The QoEmeasurement configuration 1130 may be based on a supported session leveland/or the QoS support information 1112. The QoE measurementconfiguration 1130 may facilitate providing fast and accurate renderinginformation to the vehicle UE 1104. For example, the QoE measurementconfiguration 1130 may facilitate accurate placement of augmentationcomponents for presentment at the vehicle. In some examples, the QoEmeasurement configuration 1130 may be associated with a delay and/or acapacity. For example, the QoE measurement configuration 1130 mayconfigure a delay threshold, a retransmission threshold, and/or a datarate threshold.

In some examples, the vehicle UE 1104 may collect QoE metrics based onthe QoE measurement configuration 1130. Examples of QoE metrics mayinclude a delay associated with a transmission, observed packetretransmission, and/or a data rate. In some examples, the vehicle UE1104 may transmit the XR session request 1110 when an event associatedwith QoE metrics is satisfied. For example, the vehicle UE 1104 maytransmit the XR session request 1110 when the delay exceeds the delaythreshold, observed packet retransmission exceeds the retransmissionthreshold, and/or the capacity does not satisfy the data rate threshold(e.g., the data rate is lower than allowed by the network).

FIG. 12 illustrates a communication flow 1200 between a network entity1202 and a vehicle UE 1204, as presented herein. Aspects of the networkentity 1202 may be similar to the network entity 1102 of FIG. 11 .Aspects of the vehicle UE 1204 may be similar to the vehicle UE 1104 ofFIG. 11 . In the illustrated example of FIG. 12 , the network entity1202 and the vehicle UE 1204 communicate with each other via acommunication system 1206. Aspects of the communication system 1206 maybe similar to the communication system 1106 of FIG. 11 .

As shown in FIG. 12 , the vehicle UE 1204 may output an XR sessionrequest 1210 that is obtained by the network entity 1202. Aspects of theXR session request 1210 may be implemented by the session request 722 ofFIG. 7 and/or the session request 810 of FIG. 8 . For example, the XRsession request 1210 may include vehicle information, QoS information,subscription credential information, and/or subscription requestinformation, as described in connection with FIG. 8 .

The network entity 1202 may determine a supported session level based onthe XR session request 1210, as described in connection with thesupported session level 824 of FIG. 8 . For example, the XR sessionrequest 1210 may include subscription credential information and thenetwork entity 1202 may determine a subscription level based on thesubscription credential information. The network entity 1202 may alsodetermine a supported session level based on the subscription level.

In some examples, the network entity 1202 may determine which XRservices to provide based on the subscription level. In the example ofFIG. 12 , example XR services include a navigation service 1220, alandmark service 1222, a sports service 1224, and a realtor service1226. The navigation service 1220 may facilitate providing XRinformation related to navigation (e.g., a path plan, etc.). Thelandmark service 1222 may facilitate providing XR information related toidentifying landmarks. The sports service 1224 may facilitate providingXR information related to providing additional and/or in-depthinformation related to sports-based landmarks. The realtor service 1226may facilitate providing XR information related to real estate (e.g.,information about a house that is on the market, the seller's agent,etc.).

Other examples may include additional or alternate XR services thatprovide an immersive XR experience to users, such as a passenger. Forexample, a shopping service may enable a passenger to initiate andengage in a shopping experience. A video conference service may enable apassenger to initiate and participate in a video conference. A gamingservice may enable a passenger to initiate and participate in a gamingsession with other passengers in the region (e.g., viavehicle-to-vehicle (V2V) communication).

In the example of FIG. 12 , the network entity 1202 may determine, basedon the XR session request 1210 that the user has access to certain XRservices and not to other XR services. For example, the network entity1202 may determine to provide access to the navigation service 1220, thelandmark service 1222, and the sports service 1224, and to not provideaccess to the realtor service 1226. As described above, access to thedifferent XR services may be based on the subscription level, the useridentifier, and/or based on privacy controls.

The different XR services may provide different XR information forpresentment via rendering information. For example, based on thelandmark service 1222, the network entity 1202 may provide XRinformation identifying a government building 1230 and a stadium 1232.If the user has a subscription to a sports channel, then the networkentity 1202 may determine to provide access to the sports service 1224and provide additional information related to the stadium 1232. Forexample, the XR information associated with the stadium 1232 mayindicate that a game is being played at the stadium 1232, may indicatethe current score of the game, etc. In some examples, the XR informationassociated with the stadium 1232 may provide a transaction opportunity.For example, the XR information associated with the stadium 1232 mayinclude an interactive object that facilitates purchasing a ticket to anupcoming game at the stadium 1232.

FIG. 13 illustrates a communication flow 1300 between a network entity1302 and a vehicle UE 1304, as presented herein. Aspects of the networkentity 1302 may be similar to the network entity 1102 of FIG. 11 and/orthe network entity 1202 of FIG. 12 . Aspects of the vehicle UE 1304 maybe similar to the vehicle UE 1104 of FIG. 11 and/or the vehicle UE 1204of FIG. 12 . Similar to the examples of FIG. 11 and FIG. 12 , in theillustrated example of FIG. 13 , the network entity 1302 and the vehicleUE 1304 communicate with each other via a communication system 1306.Aspects of the communication system 1306 may be similar to thecommunication system 1106 of FIG. 11 and/or the communication system1206 of FIG. 12 .

The communication flow 1300 of FIG. 13 facilitates vehicle XR sessionand service management. In some examples, the communication flow 1300may facilitate a vehicle XR session including interactive objects. Inthe example of FIG. 13 , the network entity 1302 outputs an XR sessionsetup message 1310 that is obtained by the vehicle UE 1304. Aspects ofthe XR session setup message 1310 may be implemented by the sessionresponse 728 of FIG. 7 and/or the session response 830 of FIG. 8 . Forexample, the XR session setup message 1310 may indicate a supportedsession level and/or a session configuration. In some examples, the XRsession setup message 1310 may configure one or more operationparameters at the vehicle UE 1304. For example, the XR session setupmessage 1310 may indicate a network connection type to establish (e.g.,via the communication system 1306), an update frequency associated withuplink information, etc. In some examples, the update frequency (e.g.,periodicity) may be associated with different components of the uplinkinformation. For example, the XR session setup message 1310 mayconfigure a first periodicity associated with the vehicle XR componentand a second periodicity associated with the user XR component. Thevehicle UE 1304 may collect the information associated with thedifferent XR components based on the respective periodicities. Forexample, the vehicle UE 1304 may collect information associated with thevehicle XR component based on the first periodicity and collectinformation associated with the user XR component based on the secondperiodicity.

As described above in connection with the collection procedures 732 ofFIG. 7 , the vehicle UE 1304 may collect information for the uplinkinformation via one or more sensors of the vehicle, such as the one ormore sensors 512 of FIG. 5 . The vehicle UE 1304 may output uplinkinformation 1320 that is obtained by the network entity 1302. Aspects ofthe uplink information 1320 may be implemented by the uplink information734 of FIG. 7 .

The network entity 1302 may obtain the uplink information 1320 and fuseattributes of the uplink information 1320 to generate renderinginformation, such as the rendering information 746 of FIG. 7 . Thenetwork entity 1302 may provide the rendering information to the vehicleUE 1304 for presentment via one or more displays of the vehicle, such asthe first display 510, the second display 520, the third display 522,and/or the fourth display 530 of FIG. 5 .

In some examples, the network entity 1302 may have the capability toprovide an XR service. For example, the network entity 1302 may have thecapability to provide a navigation service and a landmark service, suchas the navigation service 1220 and the landmark service 1222 of FIG. 12. In some examples, the network entity 1302 may have the capability tocommunicate with another network entity that provides an XR service. Forexample, the network entity 1302 may establish a first connection 1330to communicate with a first network entity 1332 that provides a realtorservice, such as the realtor service 1226 of FIG. 12 . The networkentity 1302 may establish a second connection 1334 to communicate with asecond network entity 1336 that provides a sports service, such as thesports service 1224 of FIG. 12 . It may be appreciated that the firstnetwork entity 1332 and the second network entity 1336 may a samenetwork entity or may be different network entities.

In the example of FIG. 13 , the rendering information provided to thevehicle UE 1304 may include an interactive object. For example, therendering information may include an interactive object 1340 that issuperimposed on a real world object (e.g., a stadium). The interactiveobject 1340 may enable a user (e.g., a passenger) to select theinteractive object 1340 and to obtain additional or in-depth informationrelated to the stadium. For example, selecting the interactive object1340 may provide additional information regarding the stadium, such as acurrent score of a game being played at the stadium.

In the example of FIG. 13 , when a user interacts with an interactiveobject, such as the interactive object 1340, the vehicle UE 1304 maygenerate user interaction information 1322 based on the interaction(s).The user interaction information 1322 may provide information regardingwhat interactive object was selected. As shown in FIG. 13 , the vehicleUE 1304 may provide the user interaction information 1322 to the networkentity 1302 via uplink information (e.g., the uplink information 1320).The network entity 1302 may then generate and output subsequentrendering information based on in part on the user interactioninformation 1322. For example, in the illustrated example of FIG. 13 ,the subsequent rendering information may include score information 1342indicating a score of a current game being played at the stadium.

In some examples, the network entity 1302 may communicate with thesecond network entity 1336 via the second connection 1334 to provide thescore information 1342. For example, the network entity 1302 may receivethe user interaction information 1322 and determine a user interactionwith the interactive object 1340. The network entity 1302 may alsodetermine that the interactive object 1340 is associated with a sportsservice being provided by the second network entity 1336. In suchexamples, the network entity 1302 may communicate with the secondnetwork entity 1336 to obtain additional information, if any, associatedwith the stadium. In the example of FIG. 13 , the second network entity1336 may identify the score information 1342 and provide the scoreinformation 1342 to the network entity 1302, for example, via the secondconnection 1334. The network entity 1302 may then generate thesubsequent rendering information including the score information 1342for presentment at the vehicle.

FIG. 14 illustrates a communication flow 1400 between a network entity1402 and a vehicle UE 1404, as presented herein. Aspects of the networkentity 1402 may be similar to the network entity 1102 of FIG. 11 , thenetwork entity 1202 of FIG. 12 , and/or the network entity 1302 of FIG.13 . Aspects of the vehicle UE 1404 may be similar to the vehicle UE1104 of FIG. 11 , the vehicle UE 1204 of FIG. 12 , and/or the vehicle UE1304 of FIG. 13 . Although not shown in the example of FIG. 14 , thenetwork entity 1402 and the vehicle UE 1404 may communicate with eachother via a communication system, such as the communication system 1106of FIG. 11 , the communication system 1206 of FIG. 12 , and/or thecommunication system 1306 of FIG. 13 .

In the illustrated example of FIG. 14 , the communication flow 1400facilitates accessing XR services provided by another network entity,such as a non-automotive XR platform 1406. The non-automotive XRplatform 1406 may provide a service that may not be associated with avehicle-based service. For example, the non-automotive XR platform 1406may provide a service, such as purchasing a ticket for a game orpurchasing a coffee.

In the illustrated example of FIG. 14 , the network entity 1402 may beconfigured to receive information from the vehicle UE 1404 and/or thenon-automotive XR platform 1406 and to process the received informationfor use by the vehicle UE 1404 and/or the non-automotive XR platform1406. For example, the vehicle UE 1404 may output uplink information1410 that is obtained by the network entity 1402. The uplink information1410 may include a vehicle XR component and a user XR component, asdescribed in connection with the vehicle XR component 920 and the firstuser XR component 932 of FIG. 9 . For example, the uplink information1410 may include information related to a velocity, a heading, userposition, XR device capability (e.g., glasses-based display, glass-lessbased display, etc.), a user profile (e.g., subscription credentials,etc.).

The network entity 1402 may then adapt the uplink information 1410 togenerate service request information 1420. The network entity 1402 mayadapt the uplink information 1410 so that the non-automotive XR platform1406 may use the service request information 1420 without being aware ofthe automotive use of the service. For example, the network entity 1402may aggregate and translate the uplink information 1410, such as theposition, direction gesture, target, etc., to generate the servicerequest information 1420. The service request information 1420 mayinclude a service request and a user profile. The network entity 1402may adapt the uplink information 1410 to generate the service requestinformation 1420 that the non-automotive XR platform 1406 may expect toreceive when receiving a service request. The network entity 1402 mayperform the translating of the uplink information 1410 based onknowledge of the vehicle, such as the make, the model, and/or additionalvehicle-specific information, such as original equipment manufacturer(OEM) information.

The network entity 1402 may then output the service request information1420 that is obtained by the non-automotive XR platform 1406. Thenon-automotive XR platform 1406 may then operate as usual based on theservice request information 1420. For example, the non-automotive XRplatform 1406 may use the service request information 1420 to generateservice output information 1430. The service output information 1430 maybe based on the service request information 1420 and without knowledgethat the service request information 1420 was generated based oninformation obtained from a vehicle and associated with a vehicle XRsession. In some examples, the service output information 1430 mayinclude data for rendering based on the service performed by thenon-automotive XR platform 1406.

The non-automotive XR platform 1406 may output the service outputinformation 1430 that is obtained by the network entity 1402. Thenetwork entity 1402 may then transcode the service output information1430 for rendering at the vehicle. For example, the network entity 1402may transcode the data obtained from the non-automotive XR platform 1406via the service output information 1430 based on one or more attributesof the uplink information 1410. For example, based on the speed,direction, the rendering capability of the vehicle UE 1404, etc., thenetwork entity 1402 may generate transcoded data 1440. The networkentity 1402 may output the transcoded data 1440 to the vehicle UE 1404for presentment via the one or more displays of the vehicle associatedwith the vehicle XR session. Aspects of the one or more displays of thevehicle may be implemented by the one or more displays of the vehicle500 of FIG. 5 (e.g., the first display 510, the second display 520, thethird display 522, and/or the fourth display 530).

In some examples, the generating of the service request information 1420and/or the transcoded data 1440 by the network entity 1402 may includecorrelating and/or compensating for differences associated with theuplink information 1410. For example, one or more attributes of theuplink information 1410 may include timing information so that thenetwork entity 1402 is able to compensate for differences, for example,between when the network entity 1402 receives the uplink information1410 and generates the transcoded data 1440. In some such examples, theuplink information 1410 may include one or more timestamps, such as thefirst timestamp 928 associated with vehicle XR component 920 and thesecond timestamp 938 associated with the first user XR component 932 ofFIG. 9 .

As one example of operation based on the communication flow 1400 of FIG.14 , the non-automotive XR platform 1406 may be associated with a coffeebusiness and may provide services associated with purchasing goods atthe coffee business, for example, via a mobile application. In suchexamples, the uplink information 1410 may include user interactioninformation, such as the user interaction information 1322 of FIG. 13 ,indicating a selection of an interactive object associated with thecoffee business (e.g., selection of a coffee offered by the coffeebusiness). The uplink information 1410 may also include informationabout the path plan of the vehicle. The network entity 1402 may use thepath plan of the vehicle and navigation services to identify a locationof the coffee business that is on the path plan. The network entity 1402may adapt the uplink information 1410, including the user interactioninformation to generate the service request information 1420 to initiatea purchase of the selected coffee. The service request information 1420may be configured with information to facilitate the coffee purchase(e.g., a coffee type, a size, etc.) and may be absent of informationrelated to the vehicle. The non-automotive XR platform 1406 may use theservice request information 1420 to perform a mobile order of theselected coffee and generate service output information 1430 that isobtained by the network entity 1402. The service output information 1430may include verification that the coffee purchase was successful and anexpected time for the coffee to be ready. The network entity 1402 maythen generate the transcoded data 1440 based on the service outputinformation 1430 and one or more attributes of the uplink information1410. For example, the transcoded data 1440 may include renderinginformation that is configured for presentment via the one or moredevices of the vehicle associated with the vehicle XR session.

Although not shown in the example of FIG. 14 , it may be appreciatedthat the communication flow 1400 between the vehicle UE 1404, thenetwork entity 1402, and the non-automotive XR platform 1406 may beimplemented via one or more application programming interfaces (APIs) orcloud native services. The APIs or cloud native services may provideexposure to one or more configuration and operation parameters. Forexample, the network entity 1402 may be configured with a first API orcloud native service that enables the vehicle UE 1404 to communicatewith the network entity 1402. The network entity 1402 may also beconfigured with a second API or cloud native service that enables thenetwork entity 1402 and the non-automotive XR platform 1406 tocommunicate. Thus, the APIs or cloud native services at the networkentity 1402 and the non-automotive XR platform 1406 may enable exposingcertain interfaces so that a service operator can provide non-automotiveservices for use via a vehicle XR session.

FIG. 15 illustrates an example communication flow 1500 between a networkentity 1502, a UE 1504, and a service entity 1506, as presented herein.Aspects of the network entity 1502 may be implanted by the cloud XRentity 708 of FIG. 7 , the network entity 802 of FIG. 8 , and/or thenetwork entity 902 of FIG. 9 . Although not shown in the illustratedexample of FIG. 15 , it may be appreciated that the network entity 1502,the UE 1504 and the service entity 1506 may be in communication via acommunication system, such as a 5G NR system.

In the illustrated example of FIG. 15 , the communication flow 1500 mayfacilitate performing a transaction associated with a service providedby the service entity 1506. For example, the service entity 1506 mayprovide a service to order a coffee from a coffee business via a mobileapplication. Aspects of the communication flow 1500 may be similar tothe communication flow 1400 of FIG. 14 .

In the example of FIG. 15 , the UE 1504 may output user interactioninformation 1510 that is obtained by the network entity 1502. The userinteraction information 1510 may be included with uplink informationthat is output to the network entity 1502. The network entity 1502 mayperform identification 1512 of a transaction interaction associated witha service. For example, the network entity 1502 may determine that theuser interaction information 1510 includes selection of an interactiveobject that facilitates a transaction. In the example of FIG. 15 , thenetwork entity 1502 may determine that the transaction is associatedwith a service that is provided by the service entity 1506. As shown inFIG. 15 , the network entity 1502 and the service entity 1506 mayperform a connection establishment procedure 1514 to facilitatecommunication with each other. The network entity 1502 may output aservice request 1516 that is obtained by the service entity 1506.Aspects of the service request 1516 may be similar to the servicerequest information 1420 of FIG. 14 . For example, the service request1516 may include information to facilitate the transaction with theservice entity 1506. The service entity 1506 may process the servicerequest 1516 and may output service information 1518 that is obtained bythe network entity 1502.

The network entity 1502 may use the service information 1518 forgenerating 1520 transaction information. In some examples, the networkentity 1502 may generate transaction information 1522 based on theservice information 1518 and uplink information. The network entity 1502outputs the transaction information 1522 that is received by the UE1504. The UE 1504 may process the transaction information 1522 forpresentment via the one or more displays of the vehicle associated withthe vehicle XR session.

For example, the user interaction information 1510 may indicateselection of an interactive object associated with a coffee business.The network entity 1502 may establish a connection with the serviceentity 1506 that facilitates performing transactions related to thecoffee business, such as ordering a coffee. The service information 1518may include a menu of products offered by the coffee business andavailable for purchase. The transaction information 1522 may includerendering information that facilitates presentment of the menu based onthe one or more displays of the vehicle. For example, the network entity1502 may adapt the transaction information 1522 based on whether therendering information will be presented via a HUD or a glasses-baseddisplay.

In some examples, a user may further engage with the renderinginformation based on the transaction information 1522. For example, therendering information may include interactive objects corresponding torespective beverages that may be purchased via the menu. The UE 1504 mayoutput uplink information including a transaction message 1524indicating selection of an interactive object corresponding to abeverage. The network entity 1502 and the service entity 1506 may thenexchange transaction communications 1526 to place the order of thebeverage. The network entity 1502 may also perform generating procedures1528 of subsequent rendering information 1530 based on the transactioncommunications 1526. The network entity 1502 may then output thesubsequent rendering information 1530 for presentment via the one ormore displays associated with the vehicle XR session.

FIG. 16 is a flowchart 1600 of a method of wireless communication. Themethod may be performed by a UE (e.g., one or more of the UEs 104,and/or an apparatus 1804 of FIG. 18 ). The method may facilitateimproving user experience associated with a vehicle XR session by usinga cloud-based entity to reduce information transmitted OTA and/or toreduce computation load associated with the vehicle XR session at theUE.

At 1602, the UE transmits a request for a vehicle XR session. Aspects ofthe request for the vehicle XR session are described in connection withat least the session request 722 of FIG. 7 . The vehicle XR session maybe based on a first user XR stream including a vehicle XR componentassociated with a vehicle and a first user XR component associated witha first user, the first user having an association with the vehicle, asdescribed in connection with the vehicle XR component 736 and the userXR component 738 of FIG. 7 . The transmitting of the request for thevehicle XR session, at 1602, may be performed by a cellular RFtransceiver 1822 and/or the vehicle XR component 198 of the apparatus1804 of FIG. 18 .

In some examples, the vehicle XR component may include at least one ofvehicle posture information, vehicle information, andvehicle-surrounding information, as described in connection with atleast the vehicle XR component 920 of FIG. 9 . In some examples, thefirst user XR component may include relative user posture informationand user input with reference to the vehicle, as described in connectionwith at least the first user XR component 932 of FIG. 9 .

At 1604, the UE transmits uplink information associated with the firstuser XR stream. Aspects of the uplink information are described inconnection with at least the uplink information 734 of FIG. 7 . Thetransmitting of the uplink information, at 1604, may be performed by thecellular RF transceiver 1822 and/or the vehicle XR component 198 of theapparatus 1804 of FIG. 18 .

At 1606, the UE receives rendering information associated with the firstuser XR stream. Aspects of the rendering information are described inconnection with at least the rendering information 746 of FIG. 7 . Thereceiving of the rendering information, at 1606, may be performed by thecellular RF transceiver 1822 and/or the vehicle XR component 198 of theapparatus 1804 of FIG. 18 .

FIG. 17 is a flowchart 1700 of a method of wireless communication. Themethod may be performed by a UE (e.g., one or more of the UEs 104,and/or an apparatus 1804 of FIG. 18 ). The method may facilitateimproving user experience associated with a vehicle XR session by usinga cloud-based entity to reduce information transmitted OTA and/or toreduce computation load associated with the vehicle XR session at theUE.

At 1702, the UE transmits a request for a vehicle XR session. Aspects ofthe request for the vehicle XR session are described in connection withat least the session request 722 of FIG. 7 . The vehicle XR session maybe based on a first user XR stream including a vehicle XR componentassociated with a vehicle and a first user XR component associated witha first user, the first user having an association with the vehicle, asdescribed in connection with the vehicle XR component 736 and the userXR component 738 of FIG. 7 . The transmitting of the request for thevehicle XR session, at 1702, may be performed by a cellular RFtransceiver 1822 and/or the vehicle XR component 198 of the apparatus1804 of FIG. 18 .

In some examples, the vehicle XR component may include at least one ofvehicle posture information, vehicle information, andvehicle-surrounding information, as described in connection with atleast the vehicle XR component 920 of FIG. 9 . In some examples, thefirst user XR component may include relative user posture informationand user input with reference to the vehicle, as described in connectionwith at least the first user XR component 932 of FIG. 9 .

In some examples, the request for the vehicle XR session, at 1702, mayinclude a subscription credential, as described in connection with thesubscription credential information 816 of FIG. 8 . In some examples,the subscription credential may be associated with a subscription level.

At 1704, the UE may collect the first user XR component associated withthe first user XR stream via one or more of an advanced driver assistantsystem (ADAS) or an in-vehicular sensor, as described in connection withthe collection procedures 732 of FIG. 7 . The collecting of the firstuser XR component, at 1704, may be performed by the vehicle XR component198 of the apparatus 1804 of FIG. 18 .

At 1706, the UE transmits uplink information associated with the firstuser XR stream. Aspects of the uplink information are described inconnection with at least the uplink information 734 of FIG. 7 . Thetransmitting of the uplink information, at 1706, may be performed by thecellular RF transceiver 1822 and/or the vehicle XR component 198 of theapparatus 1804 of FIG. 18 .

In some examples, the uplink information may include at least a firsttimestamp associated with the vehicle XR component and at least a secondtimestamp associated with the first user XR component, as described inconnection with at least the first timestamp 928 and the secondtimestamp 938 of FIG. 9 .

At 1708, the UE receives rendering information associated with the firstuser XR stream. Aspects of the rendering information are described inconnection with at least the rendering information 746 of FIG. 7 . Thereceiving of the rendering information, at 1708, may be performed by thecellular RF transceiver 1822 and/or the vehicle XR component 198 of theapparatus 1804 of FIG. 18 .

In some examples, the rendering information may include an augmentationcomponent associated with vehicle-surrounding information, as describedin connection with at least the interactive object 1340 and/or the scoreinformation 1342 of FIG. 13 .

At 1710, the UE may present the rendering information via one or moredisplays associated with the vehicle XR session. Aspects of presentingthe rendering information are described in connection with at least thepresentation procedures 748 of FIG. 7 . The presenting of the renderinginformation, at 1710, may performed by the vehicle XR component 198 ofthe apparatus 1804 of FIG. 18 .

At 1712, the UE may detect a user interaction with an interactive objectassociated with rendering information. In some examples, the first userXR component may include user interaction information associated withthe user interaction. In some examples, the interactive object may beassociated with the vehicle XR component of the vehicle XR session.Aspects of the user interaction and the user interaction information asdescribed in connection with at the user interaction information 1322 ofFIG. 13 .

In some examples, the vehicle XR session may be further based on asecond user XR stream including the vehicle XR component and a seconduser XR component associated with a second user. Aspects of the seconduser XR stream are described in connection with at least the second userXR stream 950 of FIG. 9 .

In some examples in which the vehicle XR session is based on the firstuser XR stream and the second user XR stream, the rendering information,at 1708, may include a first rendering component associated with thefirst user XR stream and a second rendering component associated withthe second user XR stream, as described in connection with at least thefirst user rendering information 940 and the second user renderinginformation 960 of FIG. 9 .

In some examples in which the vehicle XR session is based on the firstuser XR stream and the second user XR stream, the vehicle XR componentmay be shared between the first user XR stream and the second user XRstream, as described in connection with at least the vehicle XRcomponent 920, the first user XR stream 930, and the second user XRstream 950 of FIG. 9 .

FIG. 18 is a diagram 1800 illustrating an example of a hardwareimplementation for an apparatus 1804. The apparatus 1804 may be a UE, acomponent of a UE, or may implement UE functionality. In some aspects,the apparatus 1804 may include a cellular baseband processor 1824 (alsoreferred to as a modem) coupled to one or more transceivers (e.g., acellular RF transceiver 1822). The cellular baseband processor 1824 mayinclude on-chip memory 1824′. In some aspects, the apparatus 1804 mayfurther include one or more subscriber identity modules (SIM) cards 1820and an application processor 1806 coupled to a secure digital (SD) card1808 and a screen 1810. The application processor 1806 may includeon-chip memory 1806′. In some aspects, the apparatus 1804 may furtherinclude a Bluetooth module 1812, a WLAN module 1814, an SPS module 1816(e.g., GNSS module), one or more sensor modules 1818 (e.g., barometricpressure sensor/altimeter; motion sensor such as inertial measurementunit (IMU), gyroscope, and/or accelerometer(s); light detection andranging (LIDAR), radio assisted detection and ranging (RADAR), soundnavigation and ranging (SONAR), magnetometer, audio and/or othertechnologies used for positioning), additional memory modules 1826, apower supply 1830, and/or a camera 1832. The Bluetooth module 1812, theWLAN module 1814, and the SPS module 1816 may include an on-chiptransceiver (TRX) (or in some cases, just a receiver (RX)). TheBluetooth module 1812, the WLAN module 1814, and the SPS module 1816 mayinclude their own dedicated antennas and/or utilize one or more antennas1880 for communication. The cellular baseband processor 1824communicates through transceiver(s) (e.g., the cellular RF transceiver1822) via one or more antennas 1880 with one or more of the UEs 104and/or with an RU associated with a network entity 1802. The cellularbaseband processor 1824 and the application processor 1806 may eachinclude a computer-readable medium/memory, such as the on-chip memory1824′, and the on-chip memory 1806′, respectively. The additional memorymodules 1826 may also be considered a computer-readable medium/memory.Each computer-readable medium/memory (e.g., the on-chip memory 1824′,the on-chip memory 1806′, and/or the additional memory modules 1826) maybe non-transitory. The cellular baseband processor 1824 and theapplication processor 1806 are each responsible for general processing,including the execution of software stored on the computer-readablemedium/memory. The software, when executed by the cellular basebandprocessor 1824/application processor 1806, causes the cellular basebandprocessor 1824/application processor 1806 to perform the variousfunctions described supra. The computer-readable medium/memory may alsobe used for storing data that is manipulated by the cellular basebandprocessor 1824/application processor 1806 when executing software. Thecellular baseband processor 1824/application processor 1806 may be acomponent of the UE 350 and may include the memory 360 and/or at leastone of the TX processor 368, the RX processor 356, and thecontroller/processor 359. In one configuration, the apparatus 1804 maybe a processor chip (modem and/or application) and include just thecellular baseband processor 1824 and/or the application processor 1806,and in another configuration, the apparatus 1804 may be the entire UE(e.g., see the UE 350 of FIG. 3 ) and include the additional modules ofthe apparatus 1804.

As discussed supra, the vehicle XR component 198 is configured totransmit a request for a vehicle extended reality (XR) session, thevehicle XR session being based on a first user XR stream including avehicle XR component associated with a vehicle and a first user XRcomponent associated with a first user, the first user having anassociation with the vehicle. The vehicle XR component 198 is alsoconfigured to transmit uplink information associated with the first userXR stream. The vehicle XR component 198 is also configured to receiverendering information associated with the first user XR stream, therendering information being based on the uplink information.

The vehicle XR component 198 may be within the cellular basebandprocessor 1824, the application processor 1806, or both the cellularbaseband processor 1824 and the application processor 1806. The vehicleXR component 198 may be one or more hardware components specificallyconfigured to carry out the stated processes/algorithm, implemented byone or more processors configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by one or more processors, or some combination thereof.

As shown, the apparatus 1804 may include a variety of componentsconfigured for various functions. For example, the vehicle XR component198 may include one or more hardware components that perform each of theblocks of the algorithm in the flowcharts of FIGS. 16 and/or 17 .

In one configuration, the apparatus 1804, and in particular the cellularbaseband processor 1824 and/or the application processor 1806, includesmeans for transmitting a request for a vehicle extended reality (XR)session, the vehicle XR session being based on a first user XR streamincluding a vehicle XR component associated with a vehicle and a firstuser XR component associated with a first user, the first user having anassociation with the vehicle. The example apparatus 1804 also includesmeans for transmitting uplink information associated with the first userXR stream. The example apparatus 1804 also includes means for receivingrendering information associated with the first user XR stream, therendering information being based on the uplink information.

In another configuration, the example apparatus 1804 also includes meansfor presenting the rendering information via one or more displaysassociated with the vehicle XR session.

In another configuration, the example apparatus 1804 also includes meansfor collecting the first user XR component associated with the firstuser XR stream via one or more of an advanced driver assistant system(ADAS) or an in-vehicular sensor, where the uplink information includesthe first user XR component.

In another configuration, the example apparatus 1804 also includes meansfor detecting a user interaction with an interactive object associatedwith rendered information, and where the first user XR componentincludes user interaction information associated with the userinteraction.

In another configuration, the example apparatus 1804 also includes meansfor receiving subsequent rendering information based on the userinteraction information.

In another configuration, the example apparatus 1804 also includes meansfor receiving a message in response to the request, the messageincluding a configuration associated with the vehicle XR session.

In another configuration, the example apparatus 1804 also includes meansfor collecting a second user XR component associated with the seconduser XR stream, where the uplink information includes the second user XRcomponent.

In another configuration, the example apparatus 1804 also includes meansfor presenting the first rendering component via a first display of oneor more displays associated with the vehicle XR session. The exampleapparatus 1804 also includes means for presenting the second renderingcomponent via a second display of the one or more displays.

The means may be the vehicle XR component 198 of the apparatus 1804configured to perform the functions recited by the means. As describedsupra, the apparatus 1804 may include the TX processor 368, the RXprocessor 356, and the controller/processor 359. As such, in oneconfiguration, the means may be the TX processor 368, the RX processor356, and/or the controller/processor 359 configured to perform thefunctions recited by the means.

FIG. 19 is a flowchart 1900 of a method of wireless communication. Themethod may be performed by a network entity (e.g., one of the basestations 102 or a component of a base station, the cloud XR entity 708,a network entity 2102 of FIG. 21 , and/or a network entity 2260 of FIG.22 ). The method may facilitate improving user experience associatedwith a vehicle XR session by using a cloud-based entity to reduceinformation transmitted OTA and/or to reduce computation load associatedwith the vehicle XR session at the UE.

At 1902, the network entity obtains a request for a vehicle XR session.Aspects of the request for the vehicle XR session may be described inconnection with at least the session request 722 of FIG. 7 . Theobtaining of the request for the vehicle XR session, at 1902, may beperformed by the vehicle-to-cloud XR network component 199 of thenetwork entity 2102 of FIG. 21 and/or the vehicle-to-cloud XR component191 of the network entity 2260 of FIG. 22 .

At 1904, the network entity authorizes the vehicle XR session. Aspectsof authorizing the vehicle XR session may be described in connectionwith at least the authorization procedures 724 of FIG. 7 . The vehicleXR session may be based on a first user XR stream including a vehicle XRcomponent associated with a vehicle and a first user XR componentassociated with a first user, the first user having an association withthe vehicle, as described in connection with the vehicle XR component736 and the user XR component 738 of FIG. 7 . The authorizing of thevehicle XR session, at 1904, may be performed by the vehicle-to-cloud XRnetwork component 199 of the network entity 2102 of FIG. 21 and/or thevehicle-to-cloud XR component 191 of the network entity 2260 of FIG. 22.

At 1906, the network entity obtains uplink information associated withthe first user XR stream. Aspects of the uplink information aredescribed in connection with at least the uplink information 734 of FIG.7 . The obtaining of the uplink information, at 1906, may be performedby the vehicle-to-cloud XR network component 199 of the network entity2102 of FIG. 21 and/or the vehicle-to-cloud XR component 191 of thenetwork entity 2260 of FIG. 22 .

The uplink information may include the vehicle XR component and thefirst user XR component, as described in connection with the vehicle XRcomponent 736 and the user XR component 738 of FIG. 7 . In someexamples, the vehicle XR component may include at least one of vehicleposture information, vehicle information, and vehicle-surroundinginformation, as described in connection with at least the vehicle XRcomponent 920 of FIG. 9 . In some examples, the first user XR componentmay include relative user posture information and user input withreference to the vehicle, as described in connection with at least thefirst user XR component 932 of FIG. 9 .

At 1908, the network entity outputs rendering information associatedwith the first user XR stream, the rendering information being based onthe uplink information. Aspects of the rendering information aredescribed in connection with at least the rendering information 746 ofFIG. 7 . The outputting of the rendering information, at 1908, may beperformed by the vehicle-to-cloud XR network component 199 of thenetwork entity 2102 of FIG. 21 and/or the vehicle-to-cloud XR component191 of the network entity 2260 of FIG. 22 .

FIG. 20 is a flowchart 2000 of a method of wireless communication. Themethod may be performed by a network entity (e.g., one of the basestations 102 or a component of a base station, the cloud XR entity 708,a network entity 2102 of FIG. 21 , and/or a network entity 2260 of FIG.22 ). The method may facilitate improving user experience associatedwith a vehicle XR session by using a cloud-based entity to reduceinformation transmitted OTA and/or to reduce computation load associatedwith the vehicle XR session at the UE.

At 2002, the network entity obtains a request for a vehicle XR session.Aspects of the request for the vehicle XR session may be described inconnection with at least the session request 722 of FIG. 7 . Theobtaining of the request for the vehicle XR session, at 2002, may beperformed by the vehicle-to-cloud XR network component 199 of thenetwork entity 2102 of FIG. 21 and/or the vehicle-to-cloud XR component191 of the network entity 2260 of FIG. 22 .

At 2003, the network entity authorizes the vehicle XR session. Aspectsof authorizing the vehicle XR session may be described in connectionwith at least the authorization procedures 724 of FIG. 7 . The vehicleXR session may be based on a first user XR stream including a vehicle XRcomponent associated with a vehicle and a first user XR componentassociated with a first user, the first user having an association withthe vehicle, as described in connection with the vehicle XR component736 and the user XR component 738 of FIG. 7 . The authorizing of thevehicle XR session, at 2003, may be performed by the vehicle-to-cloud XRnetwork component 199 of the network entity 2102 of FIG. 21 and/or thevehicle-to-cloud XR component 191 of the network entity 2260 of FIG. 22.

In some examples, the request for the vehicle XR session, at 2002, mayinclude a subscription credential, as described in connection with thesubscription credential information 816 of FIG. 8 . In some examples,the subscription credential may be associated with a subscription level.

At 2004, the network entity obtains uplink information associated withthe first user XR stream. Aspects of the uplink information aredescribed in connection with at least the uplink information 734 of FIG.7 . The obtaining of the uplink information, at 2004, may be performedby the vehicle-to-cloud XR network component 199 of the network entity2102 of FIG. 21 and/or the vehicle-to-cloud XR component 191 of thenetwork entity 2260 of FIG. 22 .

The uplink information may include the vehicle XR component and thefirst user XR component, as described in connection with the vehicle XRcomponent 736 and the user XR component 738 of FIG. 7 . In someexamples, the vehicle XR component may include at least one of vehicleposture information, vehicle information, and vehicle-surroundinginformation, as described in connection with at least the vehicle XRcomponent 920 of FIG. 9 . In some examples, the first user XR componentmay include relative user posture information and user input withreference to the vehicle, as described in connection with at least thefirst user XR component 932 of FIG. 9 .

At 2014, the network entity outputs rendering information associatedwith the first user XR stream, the rendering information being based onthe uplink information. Aspects of the rendering information aredescribed in connection with at least the rendering information 746 ofFIG. 7 . The outputting of the rendering information, at 2014, may beperformed by the vehicle-to-cloud XR network component 199 of thenetwork entity 2102 of FIG. 21 and/or the vehicle-to-cloud XR component191 of the network entity 2260 of FIG. 22 .

At 2006, the network entity may combine the uplink information based onthe vehicle XR component and the first user XR component to generate therendering information. Aspects of combining the uplink information aredescribed in connection with at least the combination procedures 740 ofFIG. 7 . The combining of the uplink information, at 2006, may beperformed by the vehicle-to-cloud XR network component 199 of thenetwork entity 2102 of FIG. 21 and/or the vehicle-to-cloud XR component191 of the network entity 2260 of FIG. 22 .

In some examples, the uplink information (e.g., at 2004) may include atleast a first timestamp associated with the vehicle XR component and atleast a second timestamp associated with the first user XR component, asdescribed in connection with at least the first timestamp 928 and thesecond timestamp 938 of FIG. 9 . In some such examples, the networkentity may, at 2008, correlate multiple attributes of the uplinkinformation based on at least the first timestamp and the secondtimestamp, as described in connection with at least the combinationprocedures 740 of FIG. 7 . The correlating of the multiple attributes ofthe uplink information, at 2008, may be performed by thevehicle-to-cloud XR network component 199 of the network entity 2102 ofFIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

In some examples, combining the uplink information to generate therendering information (e.g., at 2006) may be based augmentationcomponents. For example, at 2010, the network entity may identify anenvironment component via the vehicle XR component of the first user XRstream. Aspects of identifying the environment component are describedin connection with at least the stadium 1232 of FIG. 12 . Theidentifying of the environment component, at 2010, may be performed bythe vehicle-to-cloud XR network component 199 of the network entity 2102of FIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

At 2012, the network entity may associate an augmentation component withvehicle-surrounding information based on the environment component tocombine the uplink information. Aspects of associating the augmentationcomponent are described in connection with at least the interactiveobject 1340 and the score information 1342 of FIG. 13 . The associatingof the augmentation component, at 2012, may be performed by thevehicle-to-cloud XR network component 199 of the network entity 2102 ofFIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

In some examples, the uplink information (e.g., at 2004) may includeuser interaction information associated with a user interaction. At2030, the network entity may output subsequent rendering informationbased on the user interaction information. Aspects of outputting thesubsequent rendering information are described in connection with atleast the score information 1342 of FIG. 13 . The outputting of thesubsequent rendering information, at 2030, may be performed by thevehicle-to-cloud XR network component 199 of the network entity 2102 ofFIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

In some examples, the user interaction information may be associatedwith a transaction. For example, at 2016, the network entity mayidentify a transaction interaction based on the user interactioninformation. The transaction interaction may be associated with aservice provided by a second network entity. Aspects of the transactioninteraction are described in connection with at least the identification1512 of FIG. 15 . The identifying of the transaction interaction, at2016, may be performed by the vehicle-to-cloud XR network component 199of the network entity 2102 of FIG. 21 and/or the vehicle-to-cloud XRcomponent 191 of the network entity 2260 of FIG. 22 .

At 2024, the network entity may output transaction information tofacilitate a transaction associated with the service. Aspects of thetransaction information are described in connection with at least thetransaction information 1522 of FIG. 15 . The outputting of thetransaction information, at 2024, may be performed by thevehicle-to-cloud XR network component 199 of the network entity 2102 ofFIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

In some examples, to facilitate the transaction associated with theservice, the network entity may communicate with the second networkentity. For example, at 2018, the network entity may establish aconnection with the second network entity based on the transactioninteraction. Aspects of establishing the connection with the secondnetwork entity are described in connection with at least the connectionestablishment procedure 1514 of FIG. 15 . The establishing of theconnection with the second network entity, at 2018, may be performed bythe vehicle-to-cloud XR network component 199 of the network entity 2102of FIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

At 2020, the network entity may obtain service information via theconnection with the second network entity. Aspects of obtaining theservice information are described in connection with at least theservice information 1518 of FIG. 15 . The obtaining of the serviceinformation, at 2020, may be performed by the vehicle-to-cloud XRnetwork component 199 of the network entity 2102 of FIG. 21 and/or thevehicle-to-cloud XR component 191 of the network entity 2260 of FIG. 22.

At 2022, the network entity may generate the transaction informationbased on the uplink information and the service information. Aspects ofgenerating the transaction information are described in connection withat least the generating 1520 of FIG. 15 . The generating of thetransaction information, at 2022, may be performed by thevehicle-to-cloud XR network component 199 of the network entity 2102 ofFIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

The network entity may then output the transaction information tofacilitate a transaction associated with the service (e.g., at 2024).

In some examples, the network entity may obtain a response based on thetransaction information. For example, at 2026, the network entity mayobtain a transaction message in response to the transaction information.Aspects of obtaining the transaction message are described in connectionwith at least the transaction message 1524 of FIG. 15 . The obtaining ofthe transaction message, at 2026, may be performed by thevehicle-to-cloud XR network component 199 of the network entity 2102 ofFIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

At 2028, the network entity may generate the subsequent renderinginformation based on the transaction message. Aspects of the subsequentrendering information are described in connection with at least thesubsequent rendering information 1530 of FIG. 15 . The generating of thesubsequent rendering information, at 2028, may be performed by thevehicle-to-cloud XR network component 199 of the network entity 2102 ofFIG. 21 and/or the vehicle-to-cloud XR component 191 of the networkentity 2260 of FIG. 22 .

In some examples, the vehicle XR session may be further based on asecond user XR stream including the vehicle XR component and a seconduser XR component associated with a second user. Aspects of the seconduser XR stream are described in connection with at least the second userXR stream 950 of FIG. 9 .

In some examples in which the vehicle XR session is based on the firstuser XR stream and the second user XR stream, the rendering information,at 2014, may include a first rendering component associated with thefirst user XR stream and a second rendering component associated withthe second user XR stream, as described in connection with at least thefirst user rendering information 940 and the second user renderinginformation 960 of FIG. 9 .

In some examples in which the vehicle XR session is based on the firstuser XR stream and the second user XR stream, the uplink information(e.g., at 2004) may include the second user XR component associated withthe second user, and the second rendering component may be based on thevehicle XR component and the second user XR component, as described inconnection with at least the second user rendering information 960 ofFIG. 9 .

In some examples in which the vehicle XR session is based on the firstuser XR stream and the second user XR stream, the vehicle XR componentmay be shared between the first user XR stream and the second user XRstream, as described in connection with at least the vehicle XRcomponent 920, the first user XR stream 930, and the second user XRstream 950 of FIG. 9 .

FIG. 21 is a diagram 2100 illustrating an example of a hardwareimplementation for a network entity 2102. The network entity 2102 may bea BS, a component of a BS, or may implement BS functionality. Thenetwork entity 2102 may include at least one of a CU 2110, a DU 2130, oran RU 2140. For example, depending on the layer functionality handled bythe vehicle-to-cloud XR network component 199, the network entity 2102may include the CU 2110; both the CU 2110 and the DU 2130; each of theCU 2110, the DU 2130, and the RU 2140; the DU 2130; both the DU 2130 andthe RU 2140; or the RU 2140. The CU 2110 may include a CU processor2112. The CU processor 2112 may include on-chip memory 2112′. In someaspects, may further include additional memory modules 2114 and acommunications interface 2118. The CU 2110 communicates with the DU 2130through a midhaul link, such as an F1 interface. The DU 2130 may includea DU processor 2132. The DU processor 2132 may include on-chip memory2132′. In some aspects, the DU 2130 may further include additionalmemory modules 2134 and a communications interface 2138. The DU 2130communicates with the RU 2140 through a fronthaul link. The RU 2140 mayinclude an RU processor 2142. The RU processor 2142 may include on-chipmemory 2142′. In some aspects, the RU 2140 may further includeadditional memory modules 2144, one or more transceivers 2146, antennas2180, and a communications interface 2148. The RU 2140 communicates withone or more of the UEs 104. The on-chip memories (e.g., the on-chipmemory 2112′, the on-chip memory 2132′, and/or the on-chip memory 2142′)and/or the additional memory modules (e.g., the additional memorymodules 2114, the additional memory modules 2134, and/or the additionalmemory modules 2144) may each be considered a computer-readablemedium/memory. Each computer-readable medium/memory may benon-transitory. Each of the CU processor 2112, the DU processor 2132,the RU processor 2142 is responsible for general processing, includingthe execution of software stored on the computer-readable medium/memory.The software, when executed by the corresponding processor(s) causes theprocessor(s) to perform the various functions described supra. Thecomputer-readable medium/memory may also be used for storing data thatis manipulated by the processor(s) when executing software.

As discussed supra, the vehicle-to-cloud XR network component 199 isconfigured to obtain a request for a vehicle XR session. Thevehicle-to-cloud XR network component 199 is also configured toauthorize the vehicle XR session, the vehicle XR session being based ona first user XR stream including a vehicle XR component associated witha vehicle and a first user XR component associated with a first user,the first user having an association with the vehicle. Thevehicle-to-cloud XR network component 199 is also configured to obtainuplink information associated with the first user XR stream. Thevehicle-to-cloud XR network component 199 is also configured to outputrendering information associated with the first user XR stream, therendering information being based on the uplink information.

The vehicle-to-cloud XR network component 199 may be within one or moreprocessors of one or more of the CU 2110, DU 2130, and the RU 2140. Thevehicle-to-cloud XR network component 199 may be one or more hardwarecomponents specifically configured to carry out the statedprocesses/algorithm, implemented by one or more processors configured toperform the stated processes/algorithm, stored within acomputer-readable medium for implementation by one or more processors,or some combination thereof.

The network entity 2102 may include a variety of components configuredfor various functions. For example, the vehicle-to-cloud XR networkcomponent 199 may include one or more hardware components that performeach of the blocks of the algorithm in the flowcharts of FIGS. 19 and/or20 .

In one configuration, the network entity 2102 includes means forobtaining a request for a vehicle extended reality (XR) session. Theexample network entity 2102 also includes means for authorizing thevehicle XR session, the vehicle XR session being based on a first userXR stream including a vehicle XR component associated with a vehicle anda first user XR component associated with a first user, the first userhaving an association with the vehicle. The example network entity 2102also includes means for obtaining uplink information associated with thefirst user XR stream. The example network entity 2102 also includesmeans for outputting rendering information associated with the firstuser XR stream, the rendering information being based on the uplinkinformation.

In another configuration, the example network entity 2102 also includesmeans for combining the uplink information based on the vehicle XRcomponent and the first user XR component to generate the renderinginformation.

In another configuration, the example network entity 2102 also includesmeans for identifying an environmental component via the vehicle XRcomponent of the first user XR stream. The example network entity 2102also includes means for associating an augmentation component withvehicle-surrounding information based on the environmental component.

In another configuration, the example network entity 2102 also includesmeans for outputting subsequent rendering information based on userinteraction information.

In another configuration, the example network entity 2102 also includesmeans for identifying a transaction interaction based on the userinteraction information, the transaction interaction associated with aservice provided by a second network entity. The example network entity2102 also includes means for outputting transaction information tofacilitate a transaction associated with the service.

In another configuration, the example network entity 2102 also includesmeans for establishing a connection with the second network entity basedon the transaction interaction. The example network entity 2102 alsoincludes means for obtaining service information via the connection withthe second network entity. The example network entity 2102 also includesmeans for generating the transaction information based on the uplinkinformation and the service information.

In another configuration, the example network entity 2102 also includesmeans for obtaining a transaction message in response to the transactioninformation. The example network entity 2102 also includes means forgenerating the subsequent rendering information based on the transactionmessage.

In another configuration, the example network entity 2102 also includesmeans for correlating multiple attributes of the uplink informationbased on at least a first timestamp and a second timestamp.

In another configuration, the example network entity 2102 also includesmeans for outputting a message in response to the request, the messageincluding a configuration associated with the vehicle XR session.

In another configuration, the example network entity 2102 also includesmeans for outputting a Quality of Experience (QoE) measurementconfiguration associated with the vehicle XR session. The examplenetwork entity 2102 also includes means for obtaining QoE metricinformation based on the QoE measurement configuration. The examplenetwork entity 2102 also includes means for adapting a rendering settingassociated with the vehicle XR session based on the QoE metricinformation. The example network entity 2102 also includes means foroutputting subsequent rendering information generated based on therendering setting.

The means may be the vehicle-to-cloud XR network component 199 of thenetwork entity 2102 configured to perform the functions recited by themeans. As described supra, the network entity 2102 may include the TXprocessor 316, the RX processor 370, and the controller/processor 375.As such, in one configuration, the means may be the TX processor 316,the RX processor 370, and/or the controller/processor 375 configured toperform the functions recited by the means.

FIG. 22 is a diagram 2200 illustrating an example of a hardwareimplementation for a network entity 2260. In one example, the networkentity 2260 may be within the core network 190. The network entity 2260may include a network processor 2212. The network processor 2212 mayinclude on-chip memory 2212′. In some aspects, the network entity 2260may further include additional memory modules 2214. The network entity2260 communicates via the network interface 2280 directly (e.g.,backhaul link) or indirectly (e.g., through a RIC) with the CU 2202. Theon-chip memory 2212′ and the additional memory modules 2214 may each beconsidered a computer-readable medium/memory. Each computer-readablemedium/memory may be non-transitory. The network processor 2212 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory. The software, whenexecuted by the corresponding processor(s) causes the processor(s) toperform the various functions described supra. The computer-readablemedium/memory may also be used for storing data that is manipulated bythe processor(s) when executing software.

As discussed supra, the vehicle-to-cloud XR component 191 is configuredto obtain a request for a vehicle XR session. The vehicle-to-cloud XRcomponent 191 is also configured to authorize the vehicle XR session,the vehicle XR session being based on a first user XR stream including avehicle XR component associated with a vehicle and a first user XRcomponent associated with a first user, the first user having anassociation with the vehicle. The vehicle-to-cloud XR component 191 isalso configured to obtain uplink information associated with the firstuser XR stream. The vehicle-to-cloud XR component 191 is also configuredto output rendering information associated with the first user XRstream, the rendering information being based on the uplink information.

The vehicle-to-cloud XR component 191 may be within the networkprocessor 2212. The vehicle-to-cloud XR component 191 may be one or morehardware components specifically configured to carry out the statedprocesses/algorithm, implemented by one or more processors configured toperform the stated processes/algorithm, stored within acomputer-readable medium for implementation by one or more processors,or some combination thereof. The network entity 2260 may include avariety of components configured for various functions.

In one configuration, the network entity 2260 includes means forobtaining a request for a vehicle extended reality (XR) session. Theexample network entity 2260 also includes means for authorizing thevehicle XR session, the vehicle XR session being based on a first userXR stream including a vehicle XR component associated with a vehicle anda first user XR component associated with a first user, the first userhaving an association with the vehicle. The example network entity 2260also includes means for obtaining uplink information associated with thefirst user XR stream. The example network entity 2260 also includesmeans for outputting rendering information associated with the firstuser XR stream, the rendering information being based on the uplinkinformation.

In another configuration, the example network entity 2260 also includesmeans for combining the uplink information based on the vehicle XRcomponent and the first user XR component to generate the renderinginformation.

In another configuration, the example network entity 2260 also includesmeans for identifying an environmental component via the vehicle XRcomponent of the first user XR stream. The example network entity 2260also includes means for associating an augmentation component withvehicle-surrounding information based on the environmental component.

In another configuration, the example network entity 2260 also includesmeans for outputting subsequent rendering information based on userinteraction information.

In another configuration, the example network entity 2260 also includesmeans for identifying a transaction interaction based on the userinteraction information, the transaction interaction associated with aservice provided by a second network entity. The example network entity2260 also includes means for outputting transaction information tofacilitate a transaction associated with the service.

In another configuration, the example network entity 2260 also includesmeans for establishing a connection with the second network entity basedon the transaction interaction. The example network entity 2260 alsoincludes means for obtaining service information via the connection withthe second network entity. The example network entity 2260 also includesmeans for generating the transaction information based on the uplinkinformation and the service information.

In another configuration, the example network entity 2260 also includesmeans for obtaining a transaction message in response to the transactioninformation. The example network entity 2260 also includes means forgenerating the subsequent rendering information based on the transactionmessage.

In another configuration, the example network entity 2260 also includesmeans for correlating multiple attributes of the uplink informationbased on at least a first timestamp and a second timestamp.

In another configuration, the example network entity 2260 also includesmeans for outputting a message in response to the request, the messageincluding a configuration associated with the vehicle XR session.

In another configuration, the example network entity 2260 also includesmeans for outputting a Quality of Experience (QoE) measurementconfiguration associated with the vehicle XR session. The examplenetwork entity 2260 also includes means for obtaining QoE metricinformation based on the QoE measurement configuration. The examplenetwork entity 2260 also includes means for adapting a rendering settingassociated with the vehicle XR session based on the QoE metricinformation. The example network entity 2260 also includes means foroutputting subsequent rendering information generated based on therendering setting.

The means may be the vehicle-to-cloud XR component 191 of the networkentity 2260 configured to perform the functions recited by the means.

It is understood that the specific order or hierarchy of blocks in theprocesses/flowcharts disclosed is an illustration of example approaches.Based upon design preferences, it is understood that the specific orderor hierarchy of blocks in the processes/flowcharts may be rearranged.Further, some blocks may be combined or omitted. The accompanying methodclaims present elements of the various blocks in a sample order, and arenot limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not limited to the aspects describedherein, but are to be accorded the full scope consistent with thelanguage claims. Reference to an element in the singular does not mean“one and only one” unless specifically so stated, but rather “one ormore.” Terms such as “if,” “when,” and “while” do not imply an immediatetemporal relationship or reaction. That is, these phrases, e.g., “when,”do not imply an immediate action in response to or during the occurrenceof an action, but simply imply that if a condition is met then an actionwill occur, but without requiring a specific or immediate timeconstraint for the action to occur. The word “exemplary” is used hereinto mean “serving as an example, instance, or illustration.” Any aspectdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects. Unless specifically statedotherwise, the term “some” refers to one or more. Combinations such as“at least one of A, B, or C,” “one or more of A, B, or C,” “at least oneof A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or anycombination thereof” include any combination of A, B, and/or C, and mayinclude multiples of A, multiples of B, or multiples of C. Specifically,combinations such as “at least one of A, B, or C,” “one or more of A, B,or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and“A, B, C, or any combination thereof” may be A only, B only, C only, Aand B, A and C, B and C, or A and B and C, where any such combinationsmay contain one or more member or members of A, B, or C. Sets should beinterpreted as a set of elements where the elements number one or more.Accordingly, for a set of X, X would include one or more elements. If afirst apparatus receives data from or transmits data to a secondapparatus, the data may be received/transmitted directly between thefirst and second apparatuses, or indirectly between the first and secondapparatuses through a set of apparatuses. All structural and functionalequivalents to the elements of the various aspects described throughoutthis disclosure that are known or later come to be known to those ofordinary skill in the art are expressly incorporated herein by referenceand are encompassed by the claims. Moreover, nothing disclosed herein isdedicated to the public regardless of whether such disclosure isexplicitly recited in the claims. The words “module,” “mechanism,”“element,” “device,” and the like may not be a substitute for the word“means.” As such, no claim element is to be construed as a means plusfunction unless the element is expressly recited using the phrase “meansfor.”

As used herein, the phrase “based on” shall not be construed as areference to a closed set of information, one or more conditions, one ormore factors, or the like. In other words, the phrase “based on A”(where “A” may be information, a condition, a factor, or the like) shallbe construed as “based at least on A” unless specifically reciteddifferently.

The following aspects are illustrative only and may be combined withother aspects or teachings described herein, without limitation.

-   -   Aspect 1 is a method of wireless communication at a UE,        including: transmitting a request for a vehicle extended reality        (XR) session, the vehicle XR session being based on a first user        XR stream including a vehicle XR component associated with a        vehicle and a first user XR component associated with a first        user, the first user having an association with the vehicle;        transmitting uplink information associated with the first user        XR stream; and receiving rendering information associated with        the first user XR stream, the rendering information being based        on the uplink information.    -   Aspect 2 is the method of aspect 1, further including:        presenting the rendering information via one or more displays        associated with the vehicle XR session.    -   Aspect 3 is the method of any of aspects 1 and 2, further        including that the vehicle XR component includes at least one of        vehicle posture information, vehicle information, and        vehicle-surrounding information.    -   Aspect 4 is the method of any of aspects 1 to 3, further        including that the first user XR component includes relative        user posture information and user input with reference to the        vehicle.    -   Aspect 5 is the method of any of aspects 1 to 4, further        including that the request for the vehicle XR session includes a        subscription credential, where the subscription credential is        associated with a subscription level.    -   Aspect 6 is the method of any of aspects 1 to 5, further        including: collecting the first user XR component associated        with the first user XR stream via one or more of an advanced        driver assistant system (ADAS) or an in-vehicular sensor, where        the uplink information includes the first user XR component.    -   Aspect 7 is the method of any of aspects 1 to 6, further        including: detecting a user interaction with an interactive        object associated with rendered information, and where the first        user XR component includes user interaction information        associated with the user interaction.    -   Aspect 8 is the method of any of aspects 1 to 7, further        including that the interactive object is associated with the        vehicle XR component of the vehicle XR session.    -   Aspect 9 is the method of any of aspects 1 to 8, further        including that the uplink information includes at least a first        timestamp associated with the vehicle XR component and at least        a second timestamp associated with the first user XR component.    -   Aspect 10 is the method of any of aspects 1 to 9, further        including that the rendering information includes an        augmentation component associated with vehicle-surrounding        information.    -   Aspect 11 is the method of any of aspects 1 to 10, further        including that the vehicle XR session is further based on a        second user XR stream including the vehicle XR component and a        second user XR component associated with a second user.    -   Aspect 12 is the method of any of aspects 1 to 11, further        including that the rendering information includes a first        rendering component associated with the first user XR stream and        a second rendering component associated with the second user XR        stream.    -   Aspect 13 is the method of any of aspects 1 to 12, further        including that the vehicle XR component is shared between the        first user XR stream and the second user XR stream.    -   Aspect 14 is an apparatus for wireless communication at a UE        including at least one processor coupled to a memory and        configured to implement any of aspects 1 to 13.    -   In aspect 15, the apparatus of aspect 14 further includes at        least one antenna coupled to the at least one processor.    -   In aspect 16, the apparatus of aspect 14 or 15 further includes        a transceiver coupled to the at least one processor.    -   Aspect 17 is an apparatus for wireless communication including        means for implementing any of aspects 1 to 13.    -   In aspect 18, the apparatus of aspect 17 further includes at        least one antenna coupled to the means to perform the method of        any of aspects 1 to 13.    -   In aspect 19, the apparatus of aspect 17 or 18 further includes        a transceiver coupled to the means to perform the method of any        of aspects 1 to 13.    -   Aspect 20 is a non-transitory computer-readable storage medium        storing computer executable code, where the code, when executed,        causes a processor to implement any of aspects 1 to 13.    -   Aspect 21 is a method of wireless communication at a network        entity, including: obtaining a request for a vehicle extended        reality (XR) session; authorizing the vehicle XR session, the        vehicle XR session being based on a first user XR stream        including a vehicle XR component associated with a vehicle and a        first user XR component associated with a first user, the first        user having an association with the vehicle; obtaining uplink        information associated with the first user XR stream; and        outputting rendering information associated with the first user        XR stream, the rendering information being based on the uplink        information.    -   Aspect 22 is the method of aspect 21, further including that the        vehicle XR component includes at least one of vehicle posture        information, vehicle information, and vehicle-surrounding        information.    -   Aspect 23 is the method of any of aspects 21 and 22, further        including that the first user XR component includes relative        user posture information and user input with reference to the        vehicle.    -   Aspect 24 is the method of any of aspects 21 to 23, further        including that the request for the vehicle XR session includes a        subscription credential, and where the subscription credential        is associated with a subscription level.    -   Aspect 25 is the method of any of aspects 21 to 24, further        including: combining the uplink information based on the vehicle        XR component and the first user XR component to generate the        rendering information.    -   Aspect 26 is the method of any of aspects 21 to 25, further        including: identifying an environmental component via the        vehicle XR component of the first user XR stream; and        associating an augmentation component with vehicle-surrounding        information based on the environmental component to combine the        uplink information.    -   Aspect 27 is the method of any of aspects 21 to 26, further        including that the uplink information includes user interaction        information associated with a user interaction, and further        including: outputting subsequent rendering information based on        the user interaction information.    -   Aspect 28 is the method of any of aspects 21 to 27, further        including that the network entity is a first network entity, and        further including: identifying a transaction interaction based        on the user interaction information, the transaction interaction        associated with a service provided by a second network entity;        and outputting transaction information to facilitate a        transaction associated with the service.    -   Aspect 29 is the method of any of aspects 21 to 28, further        including: establishing a connection with the second network        entity based on the transaction interaction; obtaining service        information via the connection with the second network entity;        and generating the transaction information based on the uplink        information and the service information.    -   Aspect 30 is the method of any of aspects 21 to 29, further        including: obtaining a transaction message in response to the        transaction information; and generating the subsequent rendering        information based on the transaction message.    -   Aspect 31 is the method of any of aspects 21 to 30, further        including that the uplink information includes at least a first        timestamp associated with the vehicle XR component and at least        a second timestamp associated with the first user XR component,        and further including: correlating multiple attributes of the        uplink information based on at least the first timestamp and the        second timestamp.    -   Aspect 32 is the method of any of aspects 21 to 31, further        including that the vehicle XR session is further based on a        second user XR stream including the vehicle XR component and a        second user XR component associated with a second user.    -   Aspect 33 is the method of any of aspects 21 to 32, further        including that the rendering information includes a first        rendering component associated with the first user XR stream and        a second rendering component associated with the second user XR        stream.    -   Aspect 34 is the method of any of aspects 21 to 33, further        including that the uplink information includes the second user        XR component associated with the second user, and the second        rendering component is based on the vehicle XR component and the        second user XR component.    -   Aspect 35 is the method of any of aspects 21 to 34, further        including that the vehicle XR component is shared between the        first user XR stream and the second user XR stream.    -   Aspect 36 is an apparatus for wireless communication at a        network entity including at least one processor coupled to a        memory and configured to implement any of aspects 21 to 35.    -   In aspect 37, the apparatus of aspect 36 further includes at        least one antenna coupled to the at least one processor.    -   In aspect 38, the apparatus of aspect 36 or 37 further includes        a transceiver coupled to the at least one processor.    -   Aspect 39 is an apparatus for wireless communication including        means for implementing any of aspects 21 to 35.    -   In aspect 40, the apparatus of aspect 39 further includes at        least one antenna coupled to the means to perform the method of        any of aspects 21 to 35.    -   In aspect 41, the apparatus of aspect 39 or 40 further includes        a transceiver coupled to the means to perform the method of any        of aspects 21 to 35.    -   Aspect 42 is a non-transitory computer-readable storage medium        storing computer executable code, where the code, when executed,        causes a processor to implement any of aspects 21 to 35.    -   Aspect 43 is a method of wireless communication at a UE,        including: transmitting a request for a vehicle XR session        associated with a vehicle, the vehicle XR session being based on        a first user XR stream including a vehicle XR component        associated with the vehicle and a first user XR component        associated with a first user; transmitting uplink information        associated with the first user XR stream; and receiving        rendering information associated with the first user XR stream,        the rendering information being based on the uplink information.    -   Aspect 44 is the method of aspect 43, further including:        presenting the rendering information via one or more displays        associated with the vehicle XR session.    -   Aspect 45 is the method of any of aspects 43 and 44, further        including that the one or more displays includes at least one of        a glasses-based display or a glasses-less display.    -   Aspect 46 is the method of any of aspects 43 to 45, further        including that the vehicle XR component includes at least one of        vehicle posture information, vehicle information, and        vehicle-surrounding information.    -   Aspect 47 is the method of any of aspects 43 to 46, further        including that the first user XR component includes relative        user posture information and user input with reference to the        vehicle.    -   Aspect 48 is the method of any of aspects 43 to 47, further        including that the request for the vehicle XR session includes a        subscription credential, where the subscription credential is        associated with a subscription level.    -   Aspect 49 is the method of any of aspects 43 to 48, further        including that the rendering information is based on the        subscription level associated with the subscription credential.    -   Aspect 50 is the method of any of aspects 43 to 49, further        including that the request for the vehicle XR session includes a        subscription request to create a subscription credential        associated with a subscription level.    -   Aspect 51 is the method of any of aspects 43 to 50, further        including that the request for the vehicle XR session includes        QoS support information for communication associated with the        vehicle XR session.    -   Aspect 52 is the method of any of aspects 43 to 51, further        including that the rendering information is based on the QoS        support information.    -   Aspect 53 is the method of any of aspects 43 to 52, further        including: collecting the first user XR component associated        with the first user XR stream via one or more of an advanced        driver assistant system (ADAS) or an in-vehicular sensor, where        the uplink information includes the first user XR component.    -   Aspect 54 is the method of any of aspects 43 to 53, further        including that the first user XR component is collected via one        or more of an advanced driver assistant system (ADAS) or an        in-vehicular sensor.    -   Aspect 55 is the method of any of aspects 43 to 54, further        including: detecting a user interaction with an interactive        object associated with rendered information, and where the first        user XR component includes user interaction information        associated with the user interaction.    -   Aspect 56 is the method of any of aspects 43 to 55, further        including: receiving subsequent rendering information based on        the user interaction information.    -   Aspect 57 is the method of any of aspects 43 to 56, further        including that the interactive object is associated with the        vehicle XR component of the vehicle XR session.    -   Aspect 58 is the method of any of aspects 43 to 47, further        including that the uplink information includes at least a first        timestamp associated with the vehicle XR component and at least        a second timestamp associated with the first user XR component.    -   Aspect 59 is the method of any of aspects 43 to 58, further        including that the uplink information is transmitted to a        network entity based on a periodicity associated with the first        user XR stream.    -   Aspect 60 is the method of any of aspects 43 to 59, further        including: receiving a message in response to the request, the        message including a configuration associated with the vehicle XR        session.    -   Aspect 61 is the method of any of aspects 43 to 60, further        including that the configuration includes one or more of: a        network connection type, an update frequency associated with the        first user XR stream, an XR session level, and a QoE measurement        configuration.    -   Aspect 62 is the method of any of aspects 43 to 61, further        including that the rendering information is based on one or more        of: a subscription level, a QoS profile, a user identifier, and        privacy controls.    -   Aspect 63 is the method of any of aspects 43 to 62, further        including that the rendering information includes an        augmentation component associated with vehicle-surrounding        information.    -   Aspect 64 is the method of any of aspects 43 to 63, further        including that the augmentation component includes one or more        of: a landmark identifier along a path plan of the vehicle, and        an interactive object.    -   Aspect 65 is the method of any of aspects 43 to 64, further        including that the vehicle XR session is further based on a        second user XR stream including the vehicle XR component and a        second user XR component associated with a second user.    -   Aspect 66 is the method of any of aspects 43 to 65, further        including: collecting the second user XR component associated        with the second user, where the uplink information includes the        second user XR component.    -   Aspect 67 is the method of any of aspects 43 to 66, further        including that the rendering information includes a first        rendering component associated with the first user XR stream and        a second rendering component associated with the second user XR        stream.    -   Aspect 68 is the method of any of aspects 43 to 67, further        including: presenting the first rendering component via a first        display of one or more displays associated with the vehicle XR        session; and presenting the second rendering component via a        second display of the one or more displays.    -   Aspect 69 is the method of any of aspects 43 to 68, further        including that the vehicle XR component is shared between the        first user XR stream and the second user XR stream.    -   Aspect 70 is an apparatus for wireless communication at a UE        including at least one processor coupled to a memory and        configured to implement any of aspects 43 to 69.    -   In aspect 71, the apparatus of aspect 70 further includes at        least one antenna coupled to the at least one processor.    -   In aspect 72, the apparatus of aspect 70 or 71 further includes        a transceiver coupled to the at least one processor.    -   Aspect 73 is an apparatus for wireless communication including        means for implementing any of aspects 43 to 69.    -   In aspect 74, the apparatus of aspect 73 further includes at        least one antenna coupled to the means to perform the method of        any of aspects 43 to 69.    -   In aspect 75, the apparatus of aspect 73 or 74 further includes        a transceiver coupled to the means to perform the method of any        of aspects 43 to 69.    -   Aspect 76 is a non-transitory computer-readable storage medium        storing computer executable code, where the code, when executed,        causes a processor to implement any of aspects 43 to 69.    -   Aspect 77 is a method of wireless communication at a network        entity, including: obtaining a request for a vehicle XR session        associated with a vehicle, the vehicle XR session being based on        a first user XR stream including a vehicle XR component        associated with the vehicle and a first user XR component        associated with a first user; obtaining uplink information        associated with the first user XR stream; and outputting        rendering information associated with the first user XR stream,        the rendering information being based on the uplink information.    -   Aspect 78 is the method of aspect 77, further including that the        vehicle XR component includes at least one of vehicle posture        information, vehicle information, and vehicle-surrounding        information.    -   Aspect 79 is the method of any of aspects 77 and 78, further        including that the first user XR component includes relative        user posture information and user input with reference to the        vehicle.    -   Aspect 80 is the method of any of aspects 77 to 79, further        including that the request for the vehicle XR session includes a        subscription credential, and where the subscription credential        is associated with a subscription level.    -   Aspect 81 is the method of any of aspects 77 to 80, further        including that the rendering information is based on the        subscription level associated with the subscription credential.    -   Aspect 82 is the method of any of aspects 77 to 81, further        including that the request for the vehicle XR session includes a        subscription request to create a subscription credential        associated with a subscription level.    -   Aspect 83 is the method of any of aspects 77 to 82, further        including that the request for the vehicle XR session includes        QoS support information for communications associated with the        vehicle XR session.    -   Aspect 84 is the method of any of aspects 77 to 83, further        including that the rendering information is based on the QoS        support information.    -   Aspect 85 is the method of any of aspects 77 to 84, further        including: combining the uplink information based on the vehicle        XR component and the first user XR component to generate the        rendering information.    -   Aspect 86 is the method of any of aspects 77 to 85, further        including combining the uplink information includes: identifying        an environmental component via the vehicle XR component of the        first user XR stream; and associating an augmentation component        with vehicle-surrounding information based on the environmental        component.    -   Aspect 87 is the method of any of aspects 77 to 86, further        including that the augmentation component includes one or more        of: a landmark identifier along a path plan of the vehicle, and        an interactive object.    -   Aspect 88 is the method of any of aspects 77 to 87, further        including that the uplink information includes user interaction        information associated with a user interaction, and further        including: outputting subsequent rendering information based on        the user interaction information.    -   Aspect 89 is the method of any of aspects 77 to 88, further        including that the network entity is a first network entity, and        further including: identifying a transaction interaction based        on the user interaction information, the transaction interaction        associated with a service provided by a second network entity;        and outputting transaction information to facilitate a        transaction associated with the service.    -   Aspect 90 is the method of any of aspects 77 to 89, further        including: establishing a connection with the second network        entity based on the transaction interaction; obtaining service        information via the connection with the second network entity;        and generating the transaction information based on the uplink        information and the service information.    -   Aspect 91 is the method of any of aspects 77 to 90, further        including: obtaining a transaction message in response to the        transaction information; and generating the subsequent rendering        information based on the transaction message.    -   Aspect 92 is the method of any of aspects 77 to 91, further        including that the uplink information includes at least a first        timestamp associated with the vehicle XR component and at least        a second timestamp associated with the first user XR component,        and further including: correlating multiple attributes of the        uplink information based on at least the first timestamp and the        second timestamp.    -   Aspect 93 is the method of any of aspects 77 to 92, further        including that the uplink information is obtained based on a        periodicity associated with the first user XR stream.    -   Aspect 94 is the method of any of aspects 77 to 93, further        including: outputting a message in response to the request, the        message including a configuration associated with the vehicle XR        session.    -   Aspect 95 is the method of any of aspects 77 to 94, further        including that the configuration includes one or more of: a        network connection type, an update frequency associated with the        first user XR stream, an XR session level, and a QoE measurement        configuration.    -   Aspect 96 is the method of any of aspects 77 to 95, further        including that the rendering information is based on one or more        of: a subscription level, a QoS profile, a user identifier, and        privacy controls.    -   Aspect 97 is the method of any of aspects 77 to 96, further        including: outputting a QoE measurement configuration associated        with the vehicle XR session; obtaining QoE metric information        based on the QoE measurement configuration; adapting a rendering        setting associated with the vehicle XR session based on the QoE        metric information; and outputting subsequent rendering        information generated based on the rendering setting.    -   Aspect 98 is the method of any of aspects 77 to 97, further        including that the vehicle XR session is further based on a        second user XR stream including the vehicle XR component and a        second user XR component associated with a second user.    -   Aspect 99 is the method of any of aspects 77 to 98, further        including that the rendering information includes a first        rendering component associated with the first user XR stream and        a second rendering component associated with the second user XR        stream.    -   Aspect 100 is the method of any of aspects 77 to 99, further        including that the uplink information includes the second user        XR component associated with the second user, and the second        rendering component is based on the vehicle XR component and the        second user XR component.    -   Aspect 101 is the method of any of aspects 77 to 100, further        including: presenting the first rendering component via a first        display of one or more displays associated with the vehicle XR        session; and presenting the second rendering component via a        second display of the one or more displays.    -   Aspect 102 is the method of any of aspects 77 to 101, further        including that the vehicle XR component is shared between the        first user XR stream and the second user XR stream.    -   Aspect 103 is the method of any of aspects 77 to 102, further        including that the first rendering component includes a first        augmentation component associated with the first user XR stream,        and the second rendering component includes a second        augmentation component associated with the second user XR        stream.    -   Aspect 104 is an apparatus for wireless communication at a        network entity including at least one processor coupled to a        memory and configured to implement any of aspects 77 to 103.    -   In aspect 105, the apparatus of aspect 104 further includes at        least one antenna coupled to the at least one processor.    -   In aspect 106, the apparatus of aspect 104 or 105 further        includes a transceiver coupled to the at least one processor.    -   Aspect 107 is an apparatus for wireless communication including        means for implementing any of aspects 77 to 103.    -   In aspect 108, the apparatus of aspect 107 further includes at        least one antenna coupled to the means to perform the method of        any of aspects 77 to 103.    -   In aspect 109, the apparatus of aspect 107 or 108 further        includes a transceiver coupled to the means to perform the        method of any of aspects 77 to 103.    -   Aspect 110 is a non-transitory computer-readable storage medium        storing computer executable code, where the code, when executed,        causes a processor to implement any of aspects 77 to 103.

What is claimed is:
 1. An apparatus for wireless communication at a userequipment (UE), comprising: a memory; and at least one processor coupledto the memory and configured to: transmit a request for a vehicleextended reality (XR) session, the vehicle XR session being based on afirst user XR stream including a vehicle XR component associated with avehicle and a first user XR component associated with a first user, thefirst user having an association with the vehicle; transmit uplinkinformation associated with the first user XR stream; and receiverendering information associated with the first user XR stream, therendering information being based on the uplink information.
 2. Theapparatus of claim 1, further comprising: at least one antenna coupledto the at least one processor, wherein the at least one processor isfurther configured to: present the rendering information via one or moredisplays associated with the vehicle XR session.
 3. The apparatus ofclaim 1, wherein the vehicle XR component includes at least one ofvehicle posture information, vehicle information, andvehicle-surrounding information.
 4. The apparatus of claim 1, whereinthe first user XR component includes relative user posture informationand user input with reference to the vehicle.
 5. The apparatus of claim1, wherein the request for the vehicle XR session includes asubscription credential, wherein the subscription credential isassociated with a subscription level.
 6. The apparatus of claim 1,wherein the at least one processor is further configured to: collect thefirst user XR component associated with the first user XR stream via oneor more of an advanced driver assistant system (ADAS) or an in-vehicularsensor, wherein the uplink information includes the first user XRcomponent.
 7. The apparatus of claim 1, wherein the at least oneprocessor is further configured to: detect a user interaction with aninteractive object associated with rendered information, and wherein thefirst user XR component includes user interaction information associatedwith the user interaction.
 8. The apparatus of claim 7, wherein theinteractive object is associated with the vehicle XR component of thevehicle XR session.
 9. The apparatus of claim 1, wherein the uplinkinformation includes at least a first timestamp associated with thevehicle XR component and at least a second timestamp associated with thefirst user XR component.
 10. The apparatus of claim 1, wherein therendering information includes an augmentation component associated withvehicle-surrounding information.
 11. The apparatus of claim 1, whereinthe vehicle XR session is further based on a second user XR streamincluding the vehicle XR component and a second user XR componentassociated with a second user.
 12. The apparatus of claim 11, whereinthe rendering information includes a first rendering componentassociated with the first user XR stream and a second renderingcomponent associated with the second user XR stream.
 13. The apparatusof claim 11, wherein the vehicle XR component is shared between thefirst user XR stream and the second user XR stream.
 14. A method ofwireless communication at a user equipment (UE), comprising:transmitting a request for a vehicle extended reality (XR) session, thevehicle XR session being based on a first user XR stream including avehicle XR component associated with a vehicle and a first user XRcomponent associated with a first user having an association with thevehicle; transmitting uplink information associated with the first userXR stream; and receiving rendering information associated with the firstuser XR stream, the rendering information being based on the uplinkinformation.
 15. An apparatus for wireless communication at a networkentity, comprising: a memory; and at least one processor coupled to thememory and configured to: obtain a request for a vehicle extendedreality (XR) session; authorize the vehicle XR session, the vehicle XRsession being based on a first user XR stream including a vehicle XRcomponent associated with a vehicle and a first user XR componentassociated with a first user having an association with the vehicle;obtain uplink information associated with the first user XR stream; andoutput rendering information associated with the first user XR stream,the rendering information being based on the uplink information.
 16. Theapparatus of claim 15, wherein the vehicle XR component includes atleast one of vehicle posture information, vehicle information, andvehicle-surrounding information.
 17. The apparatus of claim 15, whereinthe first user XR component includes relative user posture informationand user input with reference to the vehicle.
 18. The apparatus of claim15, wherein the request for the vehicle XR session includes asubscription credential, and wherein the subscription credential isassociated with a subscription level.
 19. The apparatus of claim 15,further comprising: at least one antenna coupled to the at least oneprocessor, wherein the at least one processor is further configured to:combine the uplink information based on the vehicle XR component and thefirst user XR component to generate the rendering information.
 20. Theapparatus of claim 19, wherein to combine the uplink information, the atleast one processor is further configured to: identify an environmentalcomponent via the vehicle XR component of the first user XR stream; andassociate an augmentation component with vehicle-surrounding informationbased on the environmental component.
 21. The apparatus of claim 19,wherein the uplink information includes user interaction informationassociated with a user interaction, and the at least one processor isfurther configured to: output subsequent rendering information based onthe user interaction information.
 22. The apparatus of claim 21, whereinthe network entity is a first network entity, and the at least oneprocessor is further configured to: identify a transaction interactionbased on the user interaction information, the transaction interactionassociated with a service provided by a second network entity; andoutput transaction information to facilitate a transaction associatedwith the service.
 23. The apparatus of claim 22, wherein the at leastone processor is further configured to: establish a connection with thesecond network entity based on the transaction interaction; obtainservice information via the connection with the second network entity;and generate the transaction information based on the uplink informationand the service information.
 24. The apparatus of claim 22, wherein theat least one processor is further configured to: obtain a transactionmessage in response to the transaction information; and generate thesubsequent rendering information based on the transaction message. 25.The apparatus of claim 15, wherein the uplink information includes atleast a first timestamp associated with the vehicle XR component and atleast a second timestamp associated with the first user XR component,and the at least one processor is further configured to: correlatemultiple attributes of the uplink information based on at least thefirst timestamp and the second timestamp.
 26. The apparatus of claim 15,wherein the vehicle XR session is further based on a second user XRstream including the vehicle XR component and a second user XR componentassociated with a second user.
 27. The apparatus of claim 26, whereinthe rendering information includes a first rendering componentassociated with the first user XR stream and a second renderingcomponent associated with the second user XR stream.
 28. The apparatusof claim 27, wherein the uplink information includes the second user XRcomponent associated with the second user, and the second renderingcomponent is based on the vehicle XR component and the second user XRcomponent.
 29. The apparatus of claim 26, wherein the vehicle XRcomponent is shared between the first user XR stream and the second userXR stream.
 30. A method of wireless communication at a network entity,comprising: obtaining a request for a vehicle extended reality (XR)session; authorizing the vehicle XR session, the vehicle XR sessionbeing based on a first user XR stream including a vehicle XR componentassociated with a vehicle and a first user XR component associated witha first user having an association with the vehicle; obtaining uplinkinformation associated with the first user XR stream; and outputtingrendering information associated with the first user XR stream, therendering information being based on the uplink information.